@paypal/sdk-constants
Utilities.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are PayPal-affiliated accounts added as part of team restructuring. No hostile takeover indicators present. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals are consistent with PayPal team restructuring alongside the publisher transition to sdk-integrations-npm. | ai | |
| provenance | publisher-changed | AI (provenance): PayPal consolidated SDK publishing under sdk-integrations-npm service account; this is a documented org-level transition, not a compromise. Stable for this package going forward. | ai | |
| dependencies | unvetted-dep:hi-base32 | AI (dependencies): hi-base32 is a legitimate base32 encoding library; its use in a PayPal SDK constants package is reasonable and stable across versions. | ai | |
| phantom-deps | phantom-dep:cross-domain-utils | AI (phantom-deps): cross-domain-utils is a declared dependency in this PayPal SDK constants package; indirect usage via config/build is consistent with the package's role as a constants/utilities bundle. | ai | |
| phantom-deps | phantom-dep:zalgo-promise | AI (phantom-deps): zalgo-promise is a declared dependency in this PayPal SDK constants package; indirect usage via config/build is consistent with the package's role as a constants/utilities bundle. | ai | |
| phantom-deps | phantom-dep:hi-base32 | AI (phantom-deps): hi-base32 is declared as a runtime dependency and likely used in bundled output or config; not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm packages lack it); no other indicators of supply chain compromise for this PayPal-org package. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 1.0.46 | 3 / 3 | |
| 1.0.45 | 3 / 3 | |
| 1.0.44 | 3 / 3 | |
| 1.0.43 | 3 / 3 | |
| 1.0.42 | 3 / 3 | |
| 1.0.41 | 3 / 3 | |
| 1.0.40 | 3 / 3 | |
| 1.0.39 | 3 / 3 | |
| 1.0.38 | 3 / 3 | |
| 1.0.37 | 3 / 3 | |
| 1.0.36 | 3 / 3 | |
| 1.0.35 | 3 / 3 | |
| 1.0.34 | 3 / 3 | |
| 1.0.33 | 3 / 3 | |
| 1.0.32 | 3 / 3 | |
| 1.0.31 | 3 / 3 | |
| 1.0.30 | 3 / 3 | |
| 1.0.29 | 3 / 3 | |
| 1.0.28 | 3 / 3 | |
| 1.0.27 | 3 / 3 | |
| 1.0.26 | 3 / 3 | |
| 1.0.25 | 3 / 3 | |
| 1.0.24 | 3 / 3 | |
| 1.0.23 | 3 / 3 | |
| 1.0.22 | 3 / 3 | |
| 1.0.21 | 3 / 3 | |
| 1.0.20 | 3 / 3 | |
| 1.0.19 | 3 / 3 | |
| 1.0.18 | 3 / 3 | |
| 1.0.17 | 3 / 3 |
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.