@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): No behavioral change accompanies maintainer churn; likely internal PayPal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; consistent with team rotation, not takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with zero code/script diff is inconsistent with a takeover payload. | ai | |
| dependencies | unvetted-dep:@krakenjs/post-robot | AI (dependencies): Known KrakenJS/PayPal ecosystem package; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@krakenjs/zoid | 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 | |
| dependencies | unvetted-dep:@krakenjs/jsx-pragmatic | 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 |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.59 | 8 / 22 | |
| 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 | |
| 1.0.52 | 8 / 21 | |
| 1.0.51 | 8 / 21 | |
| 1.0.50 | 8 / 21 | |
| 1.0.49 | 8 / 21 |
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.