@trustpayments/js-payments-card
TypeScript Payment Card
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:promise-polyfill | AI (phantom-deps): Declared runtime dep used via webpack bundle, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:terser-webpack-plugin | AI (phantom-deps): Build-time dep referenced in webpack config, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:ie-array-find-polyfill | AI (phantom-deps): Polyfill loaded via webpack/config for IE11 support, not directly imported. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with consistent publish history; lack of Sigstore attestation is not a disqualifier here. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx force-resolutions is a standard dependency-resolution enforcement tool; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@trustpayments/ts-luhn-check | AI (phantom-deps): Same-org package; likely consumed indirectly within the bundle. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep loaded by transpiler convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@trustpayments/ts-iin-lookup | AI (phantom-deps): Same-org package; likely consumed indirectly within the bundle. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.1093 | 2 / 24 | |
| 2.2.1090 | 2 / 24 | |
| 2.2.1081 | 4 / 24 | |
| 2.2.1074 | 4 / 27 | |
| 2.2.1073 | 4 / 27 | |
| 2.2.1071 | 4 / 27 | |
| 2.2.981 | 6 / 52 | |
| 2.2.949 | 6 / 52 | |
| 2.2.817 | 6 / 52 |
v2.2.1093
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1090
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1074
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1073
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1071
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.981
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.949
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.817
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.