@switchboard-xyz/on-demand
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Gap reflects a major version rewrite (v2→v3), not account takeover; package has 353 versions and 5 approved dependents. | ai | |
| dependencies | unvetted-dep:@coral-xyz/anchor-31 | AI (dependencies): npm alias for @coral-xyz/[email protected] — a well-known Solana framework; alias pattern is standard for multi-version support. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): `events` is a tiny Node.js core polyfill added for browser compatibility; visible in package.json browser field shim. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 14 / 22 | |
| 3.2.2 | 10 / 22 | |
| 3.2.0 | 10 / 22 | |
| 3.1.1 | 10 / 22 | |
| 3.0.0 | 10 / 22 | |
| 2.14.4 | 9 / 22 |
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.