@react-foundry/fastify-react-router
Fastify plugin for React Router.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-router/node | AI (dependencies): @react-router/node is the official React Router Node.js adapter; stable false positive for this Fastify-React-Router integration package. | ai | |
| provenance | no-provenance | AI (provenance): Absence of provenance is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 5 / 10 | |
| 0.2.4 | 5 / 10 | |
| 0.2.3 | 5 / 10 | |
| 0.2.2 | 5 / 10 | |
| 0.2.1 | 5 / 10 | |
| 0.2.0 | 5 / 10 | |
| 0.1.9 | 5 / 10 | |
| 0.1.8 | 5 / 10 | |
| 0.1.7 | 5 / 10 | |
| 0.1.6 | 5 / 10 | |
| 0.1.5 | 5 / 10 | |
| 0.1.4 | 5 / 10 | |
| 0.1.3 | 5 / 10 | |
| 0.1.2 | 5 / 10 | |
| 0.1.1 | 5 / 10 | |
| 0.1.0 | 5 / 10 |
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.