@arcgis/lumina-compiler
**No Esri Technical Support included.**
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vitest-fail-on-console | AI (phantom-deps): vitest-fail-on-console is a declared runtime dep used indirectly via vitest config; stable false positive. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Chalk is a declared runtime dep used indirectly via config/build tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): mime-types is a declared runtime dep used indirectly; stable false positive for this compiler tooling package. | ai | |
| phantom-deps | phantom-dep:js-beautify | AI (phantom-deps): js-beautify is a declared runtime dep used indirectly; stable false positive for this compiler tooling package. | ai | |
| phantom-deps | phantom-dep:sass-embedded | AI (phantom-deps): sass-embedded is a declared runtime dep used indirectly via vite/build pipeline; stable false positive. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @vitest/expect and @vitest/runner are canonical vitest sub-packages matching the declared peer dep; not suspicious. | ai | |
| provenance | publisher-changed | AI (provenance): dan11669 is an established @arcgis org publisher with 20 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @arcgis scoped package; missing repo/keywords/README detail is typical for enterprise-internal packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency, commonly used without direct imports. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.0.19 | 11 / 0 | |
| 5.0.18 | 11 / 0 | |
| 5.0.17 | 11 / 0 | |
| 5.0.16 | 11 / 0 | |
| 5.0.9 | 11 / 0 | |
| 5.0.8 | 11 / 0 | |
| 5.0.6 | 11 / 0 | |
| 5.0.5 | 11 / 0 | |
| 5.0.4 | 11 / 0 | |
| 5.0.3 | 11 / 0 | |
| 5.0.1 | 11 / 0 | |
| 5.0.0 | 11 / 0 | |
| 4.34.9 | 10 / 0 | |
| 4.34.8 | 10 / 0 | |
| 4.34.7 | 10 / 0 | |
| 4.32.16 | 16 / 0 |
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ffaubry.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.9
2 findingsThis version was published by a different npm account than previous versions on 2025-11-06. 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.
v4.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.7
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.