@x402/core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/x402Client-BSWPuNYe.d.mts | AI (source-diff): TypeScript declaration file with long type lines from tsup bundling; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/x402Client-BSWPuNYe.d.ts | AI (source-diff): TypeScript declaration file with long type lines from tsup bundling; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/x402Client-BPQrbBuD.d.mts | AI (source-diff): TypeScript declaration file with long type lines; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/x402Client-BPQrbBuD.d.ts | AI (source-diff): TypeScript declaration file with long type lines; not obfuscated. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Early-stage v0.0.1 stub from Coinbase's x402 protocol project; minimal payload and sparse metadata are expected for an initial scaffolding release. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @x402/core is the core library for the x402 Payment Protocol under the @x402 scoped namespace; the Levenshtein match against 'cors' is purely coincidental and not a typosquat. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.14.0 | 1 / 15 | |
| 2.13.0 | 1 / 15 | |
| 2.12.0 | 1 / 15 | |
| 2.11.0 | 1 / 15 | |
| 2.10.0 | 1 / 15 | |
| 2.9.0 | 1 / 15 | |
| 2.8.0 | 1 / 15 | |
| 2.7.0 | 1 / 15 | |
| 2.6.0 | 1 / 15 | |
| 2.5.0 | 1 / 15 | |
| 2.4.0 | 1 / 15 | |
| 2.3.1 | 1 / 15 | |
| 2.3.0 | 1 / 15 | |
| 2.2.0 | 1 / 15 | |
| 2.1.0 | 1 / 15 | |
| 2.0.0 | 1 / 15 | |
| 0.0.1 | 0 / 0 |
v2.14.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
2 findingsPackage name '@x402/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.