@agentcash/router
Unified route builder for Next.js App Router APIs with x402, MPP, SIWX, and API key auth
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI releases publish rapidly; expected for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is an improvement, not compromise. | ai | |
| provenance | missing-githead | AI (provenance): Likely a one-off CI/publish environment change; no other risk signals present to corroborate supply-chain concern. | ai |
Versions (showing 88 of 88)
| Version | Deps | Published |
|---|---|---|
| 1.19.1 | 10 / 13 | |
| 1.19.0 | 10 / 13 | |
| 1.18.0 | 10 / 13 | |
| 1.17.0 | 10 / 13 | |
| 1.16.0 | 10 / 13 | |
| 1.15.0 | 9 / 15 | |
| 1.14.1 | 9 / 15 | |
| 1.14.0 | 9 / 15 | |
| 1.13.0 | 9 / 15 | |
| 1.12.0 | 9 / 15 | |
| 1.11.0 | 9 / 15 | |
| 1.10.7 | 9 / 15 | |
| 1.10.6 | 8 / 15 | |
| 1.10.5 | 8 / 15 | |
| 1.10.4 | 8 / 15 | |
| 1.10.3 | 8 / 15 | |
| 1.10.2 | 8 / 15 | |
| 1.10.1 | 8 / 15 | |
| 1.10.0 | 8 / 15 | |
| 1.9.4 | 8 / 15 | |
| 1.9.3 | 8 / 15 | |
| 1.9.2 | 8 / 15 | |
| 1.9.1 | 8 / 15 | |
| 1.9.0 | 0 / 23 | |
| 1.8.0 | 0 / 23 | |
| 1.7.1 | 0 / 23 | |
| 1.7.0 | 0 / 23 | |
| 1.6.0 | 0 / 32 | |
| 1.5.2 | 0 / 32 | |
| 1.5.1 | 0 / 32 | |
| 1.5.0 | 0 / 32 | |
| 1.4.1 | 0 / 32 | |
| 1.4.0 | 0 / 32 | |
| 1.3.3 | 0 / 32 | |
| 1.3.2 | 0 / 32 | |
| 1.3.1 | 0 / 32 | |
| 1.3.0 | 0 / 32 | |
| 1.2.6 | 0 / 32 | |
| 1.2.5 | 0 / 32 | |
| 1.2.4 | 0 / 32 | |
| 1.2.3 | 0 / 32 | |
| 1.2.2 | 0 / 32 | |
| 1.2.1 | 0 / 32 | |
| 1.2.0 | 0 / 32 | |
| 1.1.10 | 0 / 32 | |
| 1.1.9 | 0 / 32 | |
| 1.1.8 | 0 / 32 | |
| 1.1.7 | 0 / 32 | |
| 1.1.6 | 0 / 32 | |
| 1.1.5 | 0 / 32 | |
| 1.1.4 | 0 / 32 | |
| 1.1.3 | 0 / 32 | |
| 1.1.2 | 0 / 32 | |
| 1.1.1 | 0 / 32 | |
| 1.1.0 | 0 / 32 | |
| 1.0.1 | 0 / 20 | |
| 1.0.0 | 0 / 20 | |
| 0.7.1 | 0 / 20 | |
| 0.7.0 | 0 / 20 | |
| 0.6.8 | 0 / 20 | |
| 0.6.7 | 0 / 20 | |
| 0.6.6 | 0 / 20 | |
| 0.6.5 | 0 / 20 | |
| 0.6.4 | 0 / 20 | |
| 0.6.3 | 0 / 20 | |
| 0.6.2 | 0 / 20 | |
| 0.6.1 | 0 / 20 | |
| 0.6.0 | 0 / 20 | |
| 0.5.2 | 0 / 20 | |
| 0.5.1 | 0 / 20 | |
| 0.5.0 | 0 / 20 | |
| 0.4.10 | 0 / 19 | |
| 0.4.9 | 0 / 19 | |
| 0.4.8 | 0 / 19 | |
| 0.4.7 | 0 / 19 | |
| 0.4.6 | 0 / 19 | |
| 0.4.5 | 0 / 19 | |
| 0.4.4 | 0 / 19 | |
| 0.4.3 | 0 / 19 | |
| 0.4.2 | 0 / 19 | |
| 0.4.1 | 0 / 18 | |
| 0.4.0 | 0 / 18 | |
| 0.3.1 | 0 / 17 | |
| 0.3.0 | 0 / 17 | |
| 0.2.2 | 0 / 17 | |
| 0.2.1 | 0 / 17 | |
| 0.2.0 | 0 / 17 | |
| 0.1.0 | 0 / 17 |
v1.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.