@lumiastream/hue-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:byte-morph | AI (phantom-deps): Declared dep; phantom-dep heuristic may miss indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@lumiastream/hue-phea-cove | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo/indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@lumiastream/lumia-rgb-utils | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo/indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Widely-used HTTP lib; likely used indirectly or via re-export in this package. | ai | |
| phantom-deps | phantom-dep:@lumiastream/network-cove | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo/indirect usage patterns. | ai | |
| provenance | no-provenance | AI (provenance): Common for this publisher/org; not a risk signal on its own. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low score driven by missing metadata, not malicious indicators; stable for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Niche internal package; missing description is stable and benign. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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.26.3 | 5 / 4 | |
| 3.22.1 | 5 / 4 | |
| 3.21.3 | 5 / 4 | |
| 3.21.1 | 5 / 4 | |
| 3.20.0 | 5 / 4 |
v3.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.26.3
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.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.