@lumiastream/lifx-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): byte-morph is declared in dependencies; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package; missing repo/keywords/description is normal for internal tooling. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 4 / 4 | |
| 3.29.1 | 4 / 4 | |
| 3.19.0 | 4 / 4 | |
| 3.18.5 | 4 / 4 | |
| 3.18.4 | 4 / 4 | |
| 3.18.3 | 4 / 4 |
v3.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.