@mintlify/http-client
The Mintlify http client package
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Mintlify transitioned publishing to GitHub Actions CI/CD automation — a standard org practice. Package is from an established company with 626 versions and no suspicious code changes. | ai | |
| provenance | no-provenance | AI (provenance): Mintlify publishes via GitHub Actions CI/CD without Sigstore attestation; consistent across all versions of this package. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Mintlify uses Elastic-2.0 across their package ecosystem; this is intentional and not a security concern. | ai |
Versions (showing 51 of 387)
| Version | Deps | Published |
|---|---|---|
| 0.0.681 | 2 / 15 | |
| 0.0.680 | 2 / 15 | |
| 0.0.679 | 2 / 15 | |
| 0.0.678 | 2 / 15 | |
| 0.0.677 | 2 / 15 | |
| 0.0.676 | 2 / 15 | |
| 0.0.675 | 2 / 15 | |
| 0.0.674 | 2 / 15 | |
| 0.0.673 | 2 / 15 | |
| 0.0.672 | 2 / 13 | |
| 0.0.671 | 2 / 13 | |
| 0.0.670 | 2 / 13 | |
| 0.0.669 | 2 / 13 | |
| 0.0.668 | 2 / 13 | |
| 0.0.667 | 2 / 13 | |
| 0.0.666 | 2 / 13 | |
| 0.0.665 | 2 / 13 | |
| 0.0.664 | 2 / 13 | |
| 0.0.663 | 2 / 15 | |
| 0.0.662 | 2 / 15 | |
| 0.0.661 | 2 / 15 | |
| 0.0.660 | 2 / 15 | |
| 0.0.659 | 2 / 15 | |
| 0.0.658 | 2 / 15 | |
| 0.0.657 | 2 / 15 | |
| 0.0.656 | 2 / 15 | |
| 0.0.655 | 2 / 15 | |
| 0.0.654 | 2 / 15 | |
| 0.0.653 | 2 / 15 | |
| 0.0.652 | 2 / 15 | |
| 0.0.651 | 2 / 15 | |
| 0.0.650 | 2 / 15 | |
| 0.0.649 | 2 / 15 | |
| 0.0.648 | 2 / 15 | |
| 0.0.647 | 2 / 15 | |
| 0.0.646 | 2 / 15 | |
| 0.0.645 | 2 / 15 | |
| 0.0.644 | 2 / 15 | |
| 0.0.643 | 2 / 15 | |
| 0.0.642 | 2 / 15 | |
| 0.0.641 | 2 / 15 | |
| 0.0.640 | 2 / 15 | |
| 0.0.639 | 2 / 15 | |
| 0.0.638 | 2 / 15 | |
| 0.0.637 | 2 / 15 | |
| 0.0.636 | 2 / 15 | |
| 0.0.635 | 2 / 15 | |
| 0.0.634 | 2 / 15 | |
| 0.0.633 | 2 / 15 | |
| 0.0.632 | 2 / 15 | |
| 0.0.631 | 2 / 15 |
v0.0.681
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.680
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.679
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.678
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.677
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.676
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.675
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.674
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.673
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.672
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.671
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.670
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.669
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.668
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.667
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.666
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.665
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.664
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.663
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.662
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.661
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.660
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.659
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.658
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.657
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.656
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.655
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.654
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.653
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.652
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.651
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.650
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.649
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.648
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.647
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.646
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.645
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.644
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.643
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.642
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.641
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.640
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.639
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.