@trustpayments/http-client
Generic http client
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
Versions (showing 51 of 290)
| Version | Deps | Published |
|---|---|---|
| 2.0.649 | 1 / 0 | |
| 2.0.648 | 1 / 0 | |
| 2.0.647 | 1 / 0 | |
| 2.0.646 | 1 / 0 | |
| 2.0.645 | 1 / 0 | |
| 2.0.644 | 1 / 0 | |
| 2.0.643 | 1 / 0 | |
| 2.0.642 | 1 / 0 | |
| 2.0.641 | 1 / 0 | |
| 2.0.640 | 1 / 0 | |
| 2.0.639 | 1 / 0 | |
| 2.0.638 | 1 / 0 | |
| 2.0.637 | 1 / 0 | |
| 2.0.636 | 1 / 0 | |
| 2.0.635 | 1 / 0 | |
| 2.0.634 | 1 / 0 | |
| 2.0.633 | 1 / 0 | |
| 2.0.632 | 1 / 0 | |
| 2.0.631 | 1 / 0 | |
| 2.0.630 | 1 / 0 | |
| 2.0.629 | 1 / 0 | |
| 2.0.628 | 1 / 0 | |
| 2.0.627 | 1 / 0 | |
| 2.0.626 | 1 / 0 | |
| 2.0.625 | 1 / 0 | |
| 2.0.624 | 1 / 0 | |
| 2.0.623 | 1 / 0 | |
| 2.0.622 | 1 / 0 | |
| 2.0.621 | 3 / 0 | |
| 2.0.620 | 3 / 0 | |
| 2.0.619 | 3 / 0 | |
| 2.0.618 | 3 / 0 | |
| 2.0.617 | 3 / 0 | |
| 2.0.616 | 3 / 0 | |
| 2.0.615 | 3 / 0 | |
| 2.0.614 | 3 / 0 | |
| 2.0.613 | 3 / 0 | |
| 2.0.612 | 3 / 0 | |
| 2.0.611 | 3 / 0 | |
| 2.0.610 | 3 / 0 | |
| 2.0.609 | 3 / 0 | |
| 2.0.608 | 3 / 0 | |
| 2.0.607 | 3 / 0 | |
| 2.0.606 | 3 / 0 | |
| 2.0.605 | 3 / 0 | |
| 2.0.604 | 3 / 0 | |
| 2.0.603 | 3 / 0 | |
| 2.0.602 | 3 / 0 | |
| 2.0.601 | 3 / 0 | |
| 2.0.600 | 3 / 0 | |
| 2.0.599 | 3 / 0 |
v2.0.649
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.648
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.647
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.646
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.645
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.644
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.643
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.642
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.641
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.640
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.639
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.638
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.637
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.636
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.635
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.634
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.633
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.632
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.631
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.630
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.629
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.628
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.627
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.626
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.625
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.624
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.623
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.621
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.620
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.619
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.617
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.616
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.615
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.614
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.613
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.611
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.610
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.609
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.608
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.607
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.606
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.605
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.604
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.602
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.601
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.600
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.599
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.