@a2a-js/sdk
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Declared dependency; used by Express middleware configuration. | ai | |
| phantom-deps | phantom-dep:@types/cors | AI (phantom-deps): Type definitions for declared cors dependency; loaded by convention. | ai | |
| phantom-deps | phantom-dep:body-parser | AI (phantom-deps): Declared dependency; used by Express middleware configuration. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type definitions for declared express dependency; loaded by convention. | ai | |
| source-diff | obfuscated-file:dist/extensions-APfrw8gz.d.cts | AI (source-diff): Auto-generated TypeScript declarations from json-schema-to-typescript; long lines are union types, not obfuscation. Stable for this package. | ai | |
| source-diff | obfuscated-file:dist/extensions-APfrw8gz.d.ts | AI (source-diff): Auto-generated TypeScript declarations from json-schema-to-typescript; long lines are union types, not obfuscation. Stable for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.3.13 | 1 / 24 | |
| 0.3.12 | 1 / 24 | |
| 0.3.11 | 1 / 24 | |
| 0.3.10 | 1 / 22 | |
| 0.3.9 | 1 / 22 | |
| 0.3.8 | 1 / 20 | |
| 0.3.7 | 1 / 20 | |
| 0.3.6 | 1 / 24 | |
| 0.3.5 | 1 / 20 | |
| 0.3.4 | 1 / 18 | |
| 0.3.3 | 1 / 18 | |
| 0.3.2 | 1 / 18 | |
| 0.3.1 | 1 / 18 | |
| 0.3.0 | 1 / 18 | |
| 0.2.5 | 6 / 16 | |
| 0.2.4 | 6 / 16 | |
| 0.2.3 | 6 / 16 | |
| 0.2.2 | 6 / 15 | |
| 0.2.1 | 6 / 15 |
v0.3.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.12
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.
v0.3.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.