redux-dynamic-modules-react
Modularize the redux app by dynamically loading reducers, state and sagas
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:redux-devtools-extension | AI (phantom-deps): Referenced in config/build files only, not directly imported — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:redux-dynamic-middlewares | AI (phantom-deps): Referenced in config/build files only, not directly imported — stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.2.3 | 3 / 17 | |
| 5.2.0 | 3 / 17 | |
| 5.1.0 | 3 / 17 | |
| 5.0.2 | 3 / 17 | |
| 5.0.1 | 3 / 17 |
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (abettadapur_msft) than the most recent previously approved version (navneetg-msft) on 2019-10-20, but abettadapur_msft is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (abettadapur_msft) than the most recent previously approved version (navneetg-msft) on 2019-08-14, but abettadapur_msft is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.