@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 51 of 130)
| Version | Deps | Published |
|---|---|---|
| 1.0.158 | 1 / 7 | |
| 1.0.157 | 1 / 7 | |
| 1.0.156 | 1 / 7 | |
| 1.0.155 | 1 / 7 | |
| 1.0.154 | 1 / 7 | |
| 1.0.153 | 1 / 7 | |
| 1.0.152 | 1 / 7 | |
| 1.0.151 | 1 / 7 | |
| 1.0.150 | 1 / 7 | |
| 1.0.149 | 1 / 7 | |
| 1.0.148 | 1 / 7 | |
| 1.0.147 | 1 / 7 | |
| 1.0.146 | 1 / 7 | |
| 1.0.145 | 1 / 7 | |
| 1.0.144 | 1 / 7 | |
| 1.0.143 | 1 / 7 | |
| 1.0.142 | 1 / 7 | |
| 1.0.141 | 1 / 7 | |
| 1.0.140 | 1 / 7 | |
| 1.0.139 | 1 / 7 | |
| 1.0.138 | 1 / 7 | |
| 1.0.137 | 1 / 7 | |
| 1.0.136 | 1 / 7 | |
| 1.0.135 | 1 / 7 | |
| 1.0.134 | 1 / 7 | |
| 1.0.133 | 1 / 7 | |
| 1.0.132 | 1 / 7 | |
| 1.0.131 | 1 / 7 | |
| 1.0.130 | 1 / 7 | |
| 1.0.129 | 1 / 7 | |
| 1.0.128 | 1 / 7 | |
| 1.0.127 | 1 / 5 | |
| 1.0.126 | 1 / 5 | |
| 1.0.125 | 1 / 5 | |
| 1.0.124 | 1 / 5 | |
| 1.0.123 | 1 / 5 | |
| 1.0.122 | 1 / 2 | |
| 1.0.121 | 1 / 2 | |
| 1.0.120 | 1 / 2 | |
| 1.0.119 | 1 / 2 | |
| 1.0.118 | 1 / 2 | |
| 1.0.117 | 1 / 2 | |
| 1.0.116 | 3 / 2 | |
| 1.0.115 | 3 / 2 | |
| 1.0.114 | 3 / 2 | |
| 1.0.113 | 3 / 3 | |
| 1.0.111 | 3 / 3 | |
| 1.0.110 | 3 / 3 | |
| 1.0.109 | 3 / 3 | |
| 1.0.108 | 3 / 3 | |
| 1.0.107 | 3 / 3 |
v1.0.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.156
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.155
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.154
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.153
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.152
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.151
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.150
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.149
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.148
2 findingsThis version was published by a different npm account than previous versions on 2024-04-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.147
2 findingsThis version was published by a different npm account than previous versions on 2024-04-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
2 findingsThis version was published by a different npm account than previous versions on 2024-04-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.145
2 findingsThis version was published by a different npm account than previous versions on 2024-03-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.144
2 findingsThis version was published by a different npm account than previous versions on 2024-03-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.143
2 findingsThis version was published by a different npm account than previous versions on 2024-03-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.142
2 findingsThis version was published by a different npm account than previous versions on 2024-02-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.141
2 findingsThis version was published by a different npm account than previous versions on 2024-02-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.140
2 findingsThis version was published by a different npm account than previous versions on 2024-02-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.139
2 findingsThis version was published by a different npm account than previous versions on 2024-02-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.138
2 findingsThis version was published by a different npm account than previous versions on 2024-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.137
2 findingsThis version was published by a different npm account than previous versions on 2024-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.136
2 findingsThis version was published by a different npm account than previous versions on 2024-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.135
2 findingsThis version was published by a different npm account than previous versions on 2023-12-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.134
2 findingsThis version was published by a different npm account than previous versions on 2023-12-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.133
2 findingsThis version was published by a different npm account than previous versions on 2023-10-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.132
2 findingsThis version was published by a different npm account than previous versions on 2023-10-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.131
2 findingsThis version was published by a different npm account than previous versions on 2023-08-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.130
2 findingsThis version was published by a different npm account than previous versions on 2023-04-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.129
2 findingsThis version was published by a different npm account than previous versions on 2023-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.128
2 findingsThis version was published by a different npm account than previous versions on 2022-11-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.127
2 findingsThis version was published by a different npm account than previous versions on 2022-10-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.126
2 findingsThis version was published by a different npm account than previous versions on 2022-10-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.125
2 findingsThis version was published by a different npm account than previous versions on 2022-10-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
2 findingsThis version was published by a different npm account than previous versions on 2022-08-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.123
2 findingsThis version was published by a different npm account than previous versions on 2022-08-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.122
2 findingsThis version was published by a different npm account than previous versions on 2022-05-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.121
2 findingsThis version was published by a different npm account than previous versions on 2022-05-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
2 findingsThis version was published by a different npm account than previous versions on 2022-05-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.119
2 findingsThis version was published by a different npm account than previous versions on 2022-04-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.118
2 findingsThis version was published by a different npm account than previous versions on 2022-03-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.117
2 findingsThis version was published by a different npm account than previous versions on 2022-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.116
2 findingsThis version was published by a different npm account than previous versions on 2022-01-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.115
2 findingsThis version was published by a different npm account than previous versions on 2022-01-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.114
2 findingsThis version was published by a different npm account than previous versions on 2022-01-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.113
2 findingsThis version was published by a different npm account than previous versions on 2021-12-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.111
2 findingsThis version was published by a different npm account than previous versions on 2021-11-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.110
2 findingsThis version was published by a different npm account than previous versions on 2021-09-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.109
2 findingsThis version was published by a different npm account than previous versions on 2021-09-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.108
2 findingsThis version was published by a different npm account than previous versions on 2021-09-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.