@lumiastream/cololight-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:axios | AI (phantom-deps): Declared dep used transitively or in compiled dist output; stable for this package. | ai | |
| phantom-deps | phantom-dep:byte-morph | AI (phantom-deps): Declared dep used transitively or in compiled dist output; stable for this package. | ai | |
| phantom-deps | phantom-dep:@lumiastream/network-cove | AI (phantom-deps): Same-org scoped dependency in monorepo; config-file reference is stable pattern. | ai | |
| phantom-deps | phantom-dep:@lumiastream/lumia-rgb-utils | AI (phantom-deps): Same-org scoped dependency in monorepo; config-file reference is stable pattern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 4 / 4 | |
| 3.29.1 | 4 / 4 | |
| 3.28.3 | 4 / 4 | |
| 3.28.1 | 4 / 4 | |
| 3.27.2 | 4 / 4 | |
| 3.24.0 | 4 / 4 | |
| 3.23.0 | 4 / 4 | |
| 3.21.3 | 4 / 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.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
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.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.