@lumiastream/homeassistant-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:electron-dns-sd | AI (dependencies): electron-dns-sd is a legitimate mDNS/DNS-SD library appropriate for a Home Assistant network discovery integration; stable dependency across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Org-scoped monorepo package; missing metadata is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this org-scoped package; not a malice signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 40 versions; package predates common provenance adoption. | ai | |
| phantom-deps | phantom-dep:@lumiastream/network-cove | AI (phantom-deps): Same-org dep likely re-exported or used indirectly; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 3 / 4 | |
| 3.29.1 | 3 / 4 | |
| 3.28.3 | 3 / 4 | |
| 3.28.1 | 3 / 4 | |
| 3.28.0 | 3 / 4 | |
| 3.27.2 | 3 / 4 | |
| 3.26.3 | 3 / 4 | |
| 3.23.0 | 3 / 4 | |
| 3.22.1 | 3 / 4 | |
| 3.22.0 | 3 / 4 | |
| 3.21.3 | 3 / 4 |
v3.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.1
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.