@trustpayments/3ds-sdk-js
This package is for internal purposes only.
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:uuid | AI (phantom-deps): Bundled SDK; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): Bundled SDK; jsdom used in test/build environment, not directly imported. | ai | |
| phantom-deps | phantom-dep:typedi | AI (phantom-deps): Bundled SDK; typedi consumed via DI framework at build time. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit polyfill dependency; stable false positive for bundled SDKs. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known implicit dependency for TypeScript decorators; stable false positive. | ai | |
| phantom-deps | phantom-dep:element-remove-polyfill | AI (phantom-deps): Polyfill consumed at build time in bundled SDK; stable false positive. | ai | |
| phantom-deps | phantom-dep:@trustpayments/http-client | AI (phantom-deps): Same-org dependency bundled into output; stable false positive for this package. | ai |
Versions (showing 51 of 373)
| Version | Deps | Published |
|---|---|---|
| 1.2.684 | 1 / 19 | |
| 1.2.683 | 1 / 19 | |
| 1.2.682 | 1 / 19 | |
| 1.2.681 | 1 / 19 | |
| 1.2.680 | 1 / 19 | |
| 1.2.679 | 1 / 19 | |
| 1.2.678 | 1 / 19 | |
| 1.2.676 | 1 / 19 | |
| 1.2.675 | 1 / 19 | |
| 1.2.674 | 1 / 19 | |
| 1.2.673 | 1 / 19 | |
| 1.2.671 | 1 / 19 | |
| 1.2.670 | 1 / 19 | |
| 1.2.669 | 1 / 19 | |
| 1.2.668 | 1 / 19 | |
| 1.2.667 | 1 / 19 | |
| 1.2.666 | 1 / 19 | |
| 1.2.665 | 1 / 19 | |
| 1.2.664 | 8 / 32 | |
| 1.2.663 | 8 / 32 | |
| 1.2.662 | 8 / 32 | |
| 1.2.660 | 8 / 32 | |
| 1.2.659 | 8 / 32 | |
| 1.2.658 | 8 / 32 | |
| 1.2.657 | 8 / 32 | |
| 1.2.656 | 8 / 32 | |
| 1.2.655 | 8 / 32 | |
| 1.2.654 | 8 / 32 | |
| 1.2.653 | 8 / 32 | |
| 1.2.652 | 8 / 32 | |
| 1.2.651 | 8 / 32 | |
| 1.2.650 | 8 / 32 | |
| 1.2.649 | 8 / 32 | |
| 1.2.648 | 8 / 32 | |
| 1.2.647 | 8 / 32 | |
| 1.2.646 | 8 / 32 | |
| 1.2.645 | 8 / 32 | |
| 1.2.643 | 8 / 32 | |
| 1.2.642 | 8 / 32 | |
| 1.2.641 | 8 / 32 | |
| 1.2.640 | 8 / 32 | |
| 1.2.639 | 8 / 32 | |
| 1.2.638 | 8 / 32 | |
| 1.2.637 | 8 / 32 | |
| 1.2.636 | 8 / 32 | |
| 1.2.635 | 8 / 32 | |
| 1.2.634 | 8 / 32 | |
| 1.2.633 | 8 / 32 | |
| 1.2.632 | 8 / 32 | |
| 1.2.631 | 8 / 32 | |
| 1.2.630 | 8 / 32 |
v1.2.684
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.683
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.682
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.681
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.680
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.679
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.678
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.676
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.675
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.674
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.673
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.671
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.670
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.669
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.668
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.667
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.666
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.665
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.664
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.663
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.662
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.660
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.659
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.658
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.657
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.656
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.655
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.654
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.653
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.651
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.650
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.649
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.648
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.647
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.646
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.645
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.643
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.642
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.641
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.640
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.639
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.638
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.637
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.636
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.635
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.634
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.633
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.632
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.631
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.630
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.