@paypal/common-components
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@krakenjs/zoid | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@krakenjs/belter | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@paypal/sdk-logos | AI (dependencies): Official PayPal SDK package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@krakenjs/post-robot | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@krakenjs/jsx-pragmatic | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@krakenjs/zalgo-promise | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.57 | 8 / 22 | |
| 1.0.56 | 8 / 22 | |
| 1.0.55 | 8 / 22 | |
| 1.0.54 | 8 / 21 | |
| 1.0.53 | 8 / 21 |
v1.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.