@exodus/redux-dependency-injection
Dependency-injection container for redux modules
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:redux | AI (phantom-deps): redux is a declared runtime dep; phantom-dep heuristic fires because it's used indirectly through the DI framework rather than directly imported. | ai | |
| dependencies | unvetted-dep:@exodus/logger | AI (dependencies): Internal Exodus org dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@exodus/typeforce | AI (dependencies): Internal Exodus org dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@exodus/dependency-types | AI (dependencies): Internal Exodus org dependency; consistent with this package's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Package explicitly sets provenance:false in publishConfig; stable policy for this org's packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 7 / 1 | |
| 4.5.0 | 7 / 1 | |
| 4.4.0 | 7 / 1 | |
| 4.3.0 | 7 / 1 | |
| 4.2.0 | 7 / 1 | |
| 4.1.2 | 8 / 0 |
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.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.
v4.2.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.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.