@exodus/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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): minimalistic-assert is a well-known, stable utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance explicitly disabled in publishConfig; intentional for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 1 / 4 | |
| 3.2.1 | 1 / 3 | |
| 3.2.0 | 1 / 3 | |
| 3.1.1 | 1 / 3 | |
| 3.1.0 | 1 / 2 | |
| 3.0.0 | 1 / 1 |
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.