@redux-saga/types
Shared types used by `redux-saga` packages.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Minor metadata gap; CI/CD provenance attestation still intact, no behavior change. | ai | |
| 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 |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.1 | 0 / 0 | |
| 1.3.0 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.4.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.2.1
1 finding[Accepted risk] 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
v1.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.