@lumiastream/tapo-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:@lumiastream/lumia-rgb-utils | AI (phantom-deps): Same-org dep used in compiled dist; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:local-devices | AI (phantom-deps): Declared dep used in compiled dist; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@network-utils/arp-lookup | AI (phantom-deps): Declared dep used in compiled dist; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@lumiastream/network-cove | AI (phantom-deps): Same-org dep used in compiled dist output; phantom-dep heuristic fires on source but not built artifacts. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared dep likely used in compiled dist; phantom-dep heuristic not reliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:crypto | AI (phantom-deps): Declared dep used in compiled dist; stable false positive for this bundled package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @lumiastream/* packages; not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Org-scoped package in an established monorepo; missing metadata is a style choice, not a malware indicator. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.30.0 | 7 / 4 | |
| 3.29.3 | 7 / 4 | |
| 3.29.2 | 7 / 4 | |
| 3.29.1 | 7 / 4 | |
| 3.28.3 | 6 / 4 | |
| 3.28.1 | 6 / 4 | |
| 3.28.0 | 6 / 4 | |
| 3.27.2 | 6 / 4 | |
| 3.26.3 | 6 / 4 | |
| 3.26.1 | 6 / 4 | |
| 3.26.0 | 6 / 4 | |
| 3.25.0 | 6 / 4 | |
| 3.24.2 | 5 / 4 | |
| 3.24.1 | 5 / 4 | |
| 3.24.0 | 5 / 4 | |
| 3.23.0 | 5 / 4 | |
| 3.22.1 | 5 / 4 | |
| 3.22.0 | 5 / 4 | |
| 3.21.3 | 5 / 4 | |
| 3.21.2 | 5 / 4 | |
| 3.21.1 | 5 / 4 | |
| 3.18.2 | 5 / 4 | |
| 3.18.1 | 5 / 4 | |
| 3.18.0 | 5 / 5 |
v3.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.