@lumiastream/tuya-cove-v2
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:p-queue | AI (phantom-deps): Declared runtime dep in a scoped org package; likely used transitively or in config-driven code. | ai | |
| phantom-deps | phantom-dep:p-retry | AI (phantom-deps): Declared runtime dep in a scoped org package; likely used transitively or in config-driven code. | ai | |
| phantom-deps | phantom-dep:p-timeout | AI (phantom-deps): Declared runtime dep in a scoped org package; likely used transitively or in config-driven code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package under @lumiastream; missing metadata is expected for private-org packages published to npm. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all 60 versions; organizational style, not a malware indicator. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.29.2 | 5 / 4 | |
| 3.29.1 | 5 / 4 | |
| 3.28.1 | 5 / 4 | |
| 3.28.0 | 5 / 4 | |
| 3.27.2 | 5 / 4 | |
| 3.26.3 | 5 / 4 | |
| 3.26.1 | 5 / 4 | |
| 3.26.0 | 5 / 4 | |
| 3.25.0 | 5 / 4 | |
| 3.24.0 | 2 / 4 | |
| 3.23.0 | 2 / 4 | |
| 3.22.1 | 2 / 4 | |
| 3.22.0 | 2 / 4 | |
| 3.21.3 | 2 / 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.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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.