@lumiastream/huev2-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org package under @lumiastream namespace; sparse metadata is consistent across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across @lumiastream org packages; not indicative of malice. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; consistent org publishing pattern. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Decodes Hue Entertainment API PSK client key from hex — standard protocol usage, not obfuscation. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 4 / 4 | |
| 3.29.1 | 4 / 4 | |
| 3.28.3 | 4 / 4 | |
| 3.28.1 | 4 / 4 | |
| 3.28.0 | 4 / 4 | |
| 3.27.2 | 4 / 4 | |
| 3.26.3 | 4 / 4 | |
| 3.24.0 | 4 / 4 | |
| 3.23.0 | 4 / 4 | |
| 3.22.1 | 4 / 4 | |
| 3.22.0 | 4 / 4 | |
| 3.21.3 | 4 / 4 | |
| 3.21.2 | 4 / 4 | |
| 3.21.1 | 4 / 4 | |
| 3.21.0 | 4 / 4 | |
| 3.20.1 | 4 / 4 | |
| 3.20.0 | 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.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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.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.