@loaders.gl/tiles
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@loaders.gl/math | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on transitive/re-exported usage patterns common in loaders.gl. | ai | |
| phantom-deps | phantom-dep:@math.gl/web-mercator | AI (phantom-deps): Companion math.gl dep; referenced in config/type files, stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 7 / 1 | |
| 4.4.2 | 7 / 1 | |
| 4.4.1 | 7 / 1 | |
| 4.4.0 | 7 / 1 | |
| 4.3.4 | 7 / 1 | |
| 4.3.3 | 7 / 1 | |
| 4.3.2 | 7 / 1 | |
| 4.3.1 | 7 / 1 | |
| 4.3.0 | 7 / 1 | |
| 4.2.5 | 7 / 1 | |
| 4.2.4 | 7 / 1 | |
| 4.2.3 | 7 / 1 | |
| 4.2.2 | 7 / 1 |
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dterekhova) than the most recent previously approved version (belom88) on 2024-10-16, but dterekhova is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dterekhova) than the most recent previously approved version (belom88) on 2024-10-01, but dterekhova is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dterekhova) than the most recent previously approved version (belom88) on 2024-09-03, but dterekhova is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.