@redux-saga/core
Saga middleware for Redux to handle Side Effects
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata gap on attested CI publish; no behavioral risk, stable across releases. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @redux-saga/core is a legitimate scoped package name, not a typosquat of 'cors'. The Levenshtein match is a false positive due to the scoped name structure. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 6 / 10 | |
| 1.5.0 | 6 / 10 | |
| 1.4.3 | 7 / 11 | |
| 1.4.1 | 7 / 11 | |
| 1.4.0 | 7 / 11 | |
| 1.3.0 | 7 / 18 | |
| 1.2.3 | 8 / 17 | |
| 1.2.2 | 8 / 17 | |
| 1.2.1 | 8 / 17 | |
| 1.2.0 | 8 / 17 | |
| 1.1.3 | 8 / 17 | |
| 1.1.2 | 8 / 17 | |
| 1.1.1 | 8 / 19 | |
| 1.1.0 | 8 / 19 | |
| 1.0.3 | 8 / 19 | |
| 1.0.2 | 8 / 19 | |
| 1.0.1 | 8 / 19 | |
| 1.0.0 | 8 / 19 |
v1.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version was published by a different npm account (redux-saga-release-bot) than the most recent previously approved version (andarist) on 2022-08-20. It has since remained available on npm for 1429 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account (redux-saga-release-bot) than the most recent previously approved version (andarist) on 2022-08-13. It has since remained available on npm for 1435 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.