@mintlify/cli
The Mintlify CLI
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Chalk is used indirectly through the CLI's output formatting; phantom dependency pattern is normal for CLI tools. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Semver is used indirectly through dependency resolution; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:front-matter | AI (phantom-deps): Front-matter is used indirectly for configuration parsing; expected for documentation CLI. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): References are in test files validating that path traversal to /etc/passwd is correctly rejected. Security test, not credential harvesting. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Standard CLI pattern: spreading process.env into child process spawn to pass environment through. Not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @mintlify/cli from established Mintlify org is not a typosquat of 'joi'. False positive from short name Levenshtein match. | ai |
Versions (showing 100 of 677)
| Version | Deps | Published |
|---|---|---|
| 4.0.684 | 16 / 16 | |
| 4.0.683 | 16 / 16 | |
| 4.0.682 | 16 / 16 | |
| 4.0.681 | 16 / 16 | |
| 4.0.680 | 16 / 16 | |
| 4.0.679 | 16 / 16 | |
| 4.0.678 | 16 / 16 | |
| 4.0.677 | 15 / 16 | |
| 4.0.676 | 15 / 16 | |
| 4.0.675 | 15 / 16 | |
| 4.0.674 | 15 / 16 | |
| 4.0.673 | 15 / 16 | |
| 4.0.672 | 15 / 16 | |
| 4.0.671 | 15 / 16 | |
| 4.0.670 | 15 / 16 | |
| 4.0.669 | 15 / 16 | |
| 4.0.668 | 15 / 16 | |
| 4.0.667 | 15 / 16 | |
| 4.0.666 | 15 / 16 | |
| 4.0.665 | 15 / 16 | |
| 4.0.664 | 15 / 16 | |
| 4.0.663 | 15 / 16 | |
| 4.0.662 | 15 / 16 | |
| 4.0.661 | 15 / 16 | |
| 4.0.660 | 15 / 16 | |
| 4.0.659 | 15 / 16 | |
| 4.0.658 | 15 / 16 | |
| 4.0.657 | 15 / 16 | |
| 4.0.656 | 15 / 16 | |
| 4.0.655 | 15 / 16 | |
| 4.0.654 | 15 / 16 | |
| 4.0.653 | 15 / 16 | |
| 4.0.652 | 15 / 16 | |
| 4.0.651 | 15 / 16 | |
| 4.0.650 | 15 / 16 | |
| 4.0.649 | 15 / 16 | |
| 4.0.648 | 15 / 16 | |
| 4.0.647 | 15 / 16 | |
| 4.0.646 | 15 / 16 | |
| 4.0.645 | 15 / 16 | |
| 4.0.644 | 15 / 16 | |
| 4.0.643 | 15 / 16 | |
| 4.0.642 | 15 / 16 | |
| 4.0.641 | 15 / 16 | |
| 4.0.640 | 15 / 16 | |
| 4.0.639 | 15 / 16 | |
| 4.0.638 | 15 / 16 | |
| 4.0.637 | 15 / 16 | |
| 4.0.636 | 15 / 16 | |
| 4.0.635 | 15 / 16 | |
| 4.0.634 | 15 / 16 | |
| 4.0.633 | 15 / 16 | |
| 4.0.632 | 15 / 16 | |
| 4.0.631 | 15 / 16 | |
| 4.0.630 | 15 / 16 | |
| 4.0.629 | 15 / 16 | |
| 4.0.628 | 15 / 16 | |
| 4.0.627 | 15 / 16 | |
| 4.0.626 | 15 / 16 | |
| 4.0.625 | 15 / 16 | |
| 4.0.624 | 15 / 16 | |
| 4.0.623 | 15 / 16 | |
| 4.0.622 | 15 / 16 | |
| 4.0.621 | 15 / 16 | |
| 4.0.620 | 15 / 16 | |
| 4.0.619 | 15 / 16 | |
| 4.0.618 | 15 / 16 | |
| 4.0.617 | 15 / 16 | |
| 4.0.616 | 15 / 16 | |
| 4.0.615 | 15 / 16 | |
| 4.0.614 | 15 / 16 | |
| 4.0.613 | 15 / 16 | |
| 4.0.612 | 15 / 16 | |
| 4.0.611 | 15 / 16 | |
| 4.0.610 | 15 / 16 | |
| 4.0.609 | 15 / 16 | |
| 4.0.608 | 15 / 16 | |
| 4.0.607 | 15 / 16 | |
| 4.0.606 | 15 / 16 | |
| 4.0.605 | 15 / 16 | |
| 4.0.604 | 14 / 16 | |
| 4.0.603 | 14 / 16 | |
| 4.0.602 | 14 / 16 | |
| 4.0.601 | 14 / 16 | |
| 4.0.600 | 14 / 16 | |
| 4.0.599 | 14 / 16 | |
| 4.0.598 | 14 / 16 | |
| 4.0.597 | 14 / 16 | |
| 4.0.596 | 14 / 16 | |
| 4.0.595 | 14 / 16 | |
| 4.0.594 | 14 / 16 | |
| 4.0.593 | 14 / 16 | |
| 4.0.592 | 14 / 16 | |
| 4.0.591 | 14 / 16 | |
| 4.0.590 | 13 / 16 | |
| 4.0.589 | 13 / 16 | |
| 4.0.588 | 13 / 16 | |
| 4.0.587 | 13 / 16 | |
| 4.0.586 | 13 / 16 | |
| 4.0.585 | 13 / 16 |
v4.0.684
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.683
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.682
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.681
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.680
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.679
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.678
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.677
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.676
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.675
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.674
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.673
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.672
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.671
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.670
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.669
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.668
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.667
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.666
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.665
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.664
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.663
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.662
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.661
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.660
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.659
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.658
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.657
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.656
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.655
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.654
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.653
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.651
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.650
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.649
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.648
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.647
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.646
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.645
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.644
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.643
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.642
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.641
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.640
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.639
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.638
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.637
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.636
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.635
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.634
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.633
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.632
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.631
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.630
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.629
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.628
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.627
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.626
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.625
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.624
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.623
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.622
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.621
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.620
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.619
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.618
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.617
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.616
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.615
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.613
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.612
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.610
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.609
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.608
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.607
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.606
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.605
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.604
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.603
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.602
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.601
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.600
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.599
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.598
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.597
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.596
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.595
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.594
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.593
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.592
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.591
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.590
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.589
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.588
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.587
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.586
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.585
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.