@enhavo/dependency-injection
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rollup/pluginutils | AI (phantom-deps): Declared dependency; phantom-dep heuristic is not authoritative for framework-scoped packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.15.13 | 6 / 1 | |
| 0.15.12 | 6 / 1 | |
| 0.15.11 | 6 / 1 | |
| 0.15.10 | 6 / 1 | |
| 0.15.9 | 6 / 1 | |
| 0.15.8 | 6 / 1 | |
| 0.15.7 | 6 / 1 | |
| 0.15.6 | 6 / 1 | |
| 0.15.5 | 6 / 1 | |
| 0.15.4 | 6 / 1 | |
| 0.15.3 | 6 / 1 | |
| 0.15.2 | 6 / 1 | |
| 0.15.1 | 6 / 1 | |
| 0.14.7 | 6 / 1 | |
| 0.14.6 | 6 / 1 | |
| 0.14.5 | 6 / 1 | |
| 0.14.3 | 6 / 1 | |
| 0.14.2 | 6 / 1 | |
| 0.13.6 | 5 / 1 | |
| 0.12.6 | 5 / 1 |
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.