@paypal/sdk-logos
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established PayPal SDK package; provenance not yet adopted by this publisher across their packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.3.7 | 3 / 13 | |
| 2.3.6 | 3 / 13 | |
| 2.3.5 | 3 / 13 | |
| 2.3.4 | 3 / 13 | |
| 2.3.3 | 3 / 13 | |
| 2.3.2 | 3 / 13 | |
| 2.3.1 | 3 / 13 | |
| 2.3.0 | 3 / 13 | |
| 2.2.16 | 3 / 13 | |
| 2.2.15 | 3 / 13 | |
| 2.2.14 | 3 / 13 | |
| 2.2.13 | 3 / 13 | |
| 2.2.12 | 3 / 13 | |
| 2.2.11 | 3 / 13 | |
| 2.2.10 | 3 / 13 | |
| 2.2.9 | 3 / 13 | |
| 2.2.8 | 3 / 13 |
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.