@redux-saga/types
Shared types used by `redux-saga` packages.
3
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
andaristyelouafi
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migration from redux-saga-release-bot to GitHub Actions CI with SLSA provenance; legitimate CI update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old bot account removed as part of CI migration to GitHub Actions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @redux-saga/types is a legitimate types-only sub-package of the redux-saga monorepo. Empty JS entry, no deps, short README, and inflated semver are all expected characteristics of this package type. | ai | |
| provenance | no-provenance | AI (provenance): redux-saga uses a release bot for publishing; lack of Sigstore provenance is consistent with their existing release pipeline and not a security concern here. | ai |
v1.4.0
2 findings
HIGH
Publisher changed: redux-saga-release-bot → GitHub Actions (on 2026-05-21)
provenance
This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
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 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.