@iobroker/db-objects-jsonl
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:deep-clone | AI (phantom-deps): deep-clone is declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.2.2 | 6 / 0 | |
| 7.2.1 | 6 / 0 | |
| 7.2.0 | 6 / 0 | |
| 7.1.2 | 6 / 0 | |
| 7.1.1 | 6 / 0 | |
| 7.1.0 | 6 / 0 | |
| 7.0.7 | 6 / 0 | |
| 7.0.6 | 6 / 0 | |
| 7.0.5 | 6 / 0 | |
| 7.0.4 | 6 / 0 | |
| 7.0.3 | 6 / 0 | |
| 7.0.2 | 6 / 0 | |
| 7.0.1 | 6 / 0 | |
| 7.0.0 | 6 / 0 |
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.