@lumiastream/razer-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): Axios is a legitimate HTTP client; phantom-dep heuristic doesn't apply to transitive imports. | ai | |
| phantom-deps | phantom-dep:sockette | AI (phantom-deps): Sockette is a WebSocket utility; phantom-dep heuristic doesn't apply to transitive imports. | ai | |
| phantom-deps | phantom-dep:@lumiastream/network-cove | AI (phantom-deps): Same-org scoped dependency; monorepo internal reference pattern. | ai | |
| phantom-deps | phantom-dep:@lumiastream/lumia-rgb-utils | AI (phantom-deps): Same-org scoped dependency; monorepo internal reference pattern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 4 / 4 | |
| 3.29.1 | 4 / 4 | |
| 3.28.1 | 4 / 4 | |
| 3.28.0 | 4 / 4 | |
| 3.27.2 | 4 / 4 | |
| 3.22.0 | 4 / 4 | |
| 3.17.2 | 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.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.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.