@lumiastream/nanoleaf-cove
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @lumiastream scoped package; no provenance is consistent across all 53 versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal library in an established org; missing metadata is typical for private/org packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across lumiastream scoped packages; not a spam indicator here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.30.0 | 5 / 4 | |
| 3.29.3 | 5 / 4 | |
| 3.29.2 | 5 / 4 | |
| 3.29.1 | 5 / 4 | |
| 3.28.3 | 5 / 4 | |
| 3.28.1 | 5 / 4 | |
| 3.28.0 | 5 / 4 | |
| 3.27.2 | 5 / 4 | |
| 3.23.0 | 5 / 4 | |
| 3.22.1 | 5 / 4 | |
| 3.22.0 | 5 / 4 | |
| 3.21.3 | 5 / 4 |
v3.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.