@arcgis/lumina
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Esri proprietary license referenced via LICENSE.md; standard for @arcgis packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped enterprise package; missing description/repo/keywords is a style issue, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped ArcGIS package; no description is a style issue, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; not specific to this release. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lit-labs/ssr-client | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.0.19 | 3 / 0 | |
| 5.0.18 | 3 / 0 | |
| 5.0.17 | 3 / 0 | |
| 5.0.16 | 3 / 0 | |
| 5.0.15 | 3 / 0 | |
| 5.0.14 | 3 / 0 | |
| 5.0.13 | 3 / 0 | |
| 5.0.12 | 3 / 0 | |
| 5.0.11 | 3 / 0 | |
| 5.0.10 | 3 / 0 | |
| 5.0.9 | 3 / 0 | |
| 5.0.8 | 3 / 0 | |
| 5.0.7 | 3 / 0 | |
| 5.0.6 | 3 / 0 | |
| 5.0.5 | 3 / 0 | |
| 5.0.4 | 3 / 0 | |
| 5.0.3 | 3 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.34.9 | 3 / 0 | |
| 4.34.8 | 3 / 0 | |
| 4.34.7 | 3 / 0 | |
| 4.34.6 | 3 / 0 | |
| 4.34.5 | 3 / 0 | |
| 4.32.16 | 8 / 0 |
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.