@resourge/react-fetch
[](LICENSE)
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 | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — legitimate CI/CD migration for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by automated CI/CD publish with SLSA attestation; consistent with project resuming development under automation. | ai | |
| dependencies | unvetted-dep:@resourge/history-store | AI (dependencies): Same-org sibling dependency from the resourge monorepo; consistent publisher identity across all @resourge/* packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.49.0 | 3 / 0 | |
| 1.48.0 | 3 / 0 | |
| 1.43.1 | 3 / 0 | |
| 1.43.0 | 3 / 0 | |
| 1.42.2 | 3 / 0 | |
| 1.42.1 | 3 / 0 | |
| 1.42.0 | 3 / 0 | |
| 1.41.7 | 3 / 0 | |
| 1.41.6 | 3 / 0 | |
| 1.41.5 | 3 / 0 | |
| 1.41.4 | 3 / 0 | |
| 1.41.3 | 3 / 0 | |
| 1.41.2 | 3 / 0 | |
| 1.41.1 | 3 / 0 | |
| 1.41.0 | 3 / 0 | |
| 1.40.0 | 3 / 0 |
v1.48.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.