@mintlify/common
Commonly shared code within Mintlify
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are canonical remark/rehype ecosystem packages consistent with existing unified stack; no malicious signal. | ai | |
| dependencies | unvetted-dep:color-blend | AI (dependencies): color-blend is a legitimate color manipulation utility; appropriate for a UI/documentation library. | ai | |
| dependencies | unvetted-dep:@types/mdast | AI (dependencies): Type definitions package from DefinitelyTyped; no runtime risk, appropriate for a markdown processing library. | ai | |
| dependencies | unvetted-dep:@mintlify/mdx | AI (dependencies): First-party Mintlify package; same organization as this package. | ai | |
| dependencies | unvetted-dep:@asyncapi/specs | AI (dependencies): Official AsyncAPI specification package from the AsyncAPI Initiative; legitimate for API documentation tooling. | ai | |
| dependencies | unvetted-dep:@asyncapi/parser | AI (dependencies): Official AsyncAPI parser from the AsyncAPI Initiative; legitimate for API documentation tooling. | ai | |
| dependencies | unvetted-dep:@mintlify/models | AI (dependencies): First-party Mintlify package; same organization as this package. | ai | |
| dependencies | unvetted-dep:hex-rgb | AI (dependencies): hex-rgb is a well-known, single-purpose utility package by sindresorhus ecosystem; legitimate dependency for color processing. | ai | |
| dependencies | unvetted-dep:@mintlify/openapi-parser | AI (dependencies): First-party Mintlify package; same organization as this package. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): Type-only package; framework-scoped usage is expected for TypeScript projects using mdast types. | ai | |
| phantom-deps | phantom-dep:@asyncapi/specs | AI (phantom-deps): Config-referenced usage is expected for AsyncAPI spec validation; not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:hast-util-to-text | AI (phantom-deps): Config-referenced in a markdown/MDX processing library; indirect usage pattern is legitimate. | ai | |
| phantom-deps | phantom-dep:micromark-extension-mdx-jsx | AI (phantom-deps): Config-referenced in a markdown/MDX processing library; indirect usage pattern is legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 858 versions and 230k weekly downloads; lack of provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@mintlify/validation | AI (dependencies): First-party Mintlify package; same organization as this package. | ai |
Versions (showing 100 of 394)
| Version | Deps | Published |
|---|---|---|
| 1.0.723 | 48 / 15 | |
| 1.0.722 | 48 / 15 | |
| 1.0.705 | 47 / 15 | |
| 1.0.649 | 47 / 15 | |
| 1.0.648 | 43 / 16 | |
| 1.0.647 | 43 / 16 | |
| 1.0.646 | 43 / 16 | |
| 1.0.645 | 43 / 16 | |
| 1.0.644 | 43 / 16 | |
| 1.0.643 | 43 / 16 | |
| 1.0.642 | 43 / 16 | |
| 1.0.641 | 44 / 16 | |
| 1.0.640 | 44 / 16 | |
| 1.0.639 | 44 / 16 | |
| 1.0.638 | 43 / 16 | |
| 1.0.637 | 43 / 16 | |
| 1.0.636 | 43 / 16 | |
| 1.0.635 | 43 / 16 | |
| 1.0.634 | 43 / 16 | |
| 1.0.633 | 43 / 16 | |
| 1.0.632 | 43 / 16 | |
| 1.0.631 | 43 / 16 | |
| 1.0.630 | 43 / 16 | |
| 1.0.629 | 43 / 16 | |
| 1.0.628 | 43 / 16 | |
| 1.0.627 | 43 / 16 | |
| 1.0.626 | 43 / 16 | |
| 1.0.625 | 43 / 16 | |
| 1.0.624 | 43 / 16 | |
| 1.0.623 | 43 / 16 | |
| 1.0.622 | 43 / 16 | |
| 1.0.621 | 43 / 16 | |
| 1.0.620 | 43 / 16 | |
| 1.0.619 | 43 / 16 | |
| 1.0.618 | 43 / 16 | |
| 1.0.617 | 43 / 16 | |
| 1.0.616 | 43 / 16 | |
| 1.0.615 | 43 / 16 | |
| 1.0.614 | 43 / 16 | |
| 1.0.613 | 43 / 16 | |
| 1.0.612 | 42 / 16 | |
| 1.0.611 | 42 / 16 | |
| 1.0.610 | 42 / 16 | |
| 1.0.609 | 42 / 16 | |
| 1.0.608 | 42 / 16 | |
| 1.0.607 | 42 / 16 | |
| 1.0.606 | 42 / 16 | |
| 1.0.605 | 42 / 16 | |
| 1.0.604 | 42 / 16 | |
| 1.0.603 | 42 / 16 | |
| 1.0.602 | 42 / 16 | |
| 1.0.601 | 42 / 16 | |
| 1.0.600 | 42 / 16 | |
| 1.0.599 | 42 / 16 | |
| 1.0.598 | 42 / 16 | |
| 1.0.597 | 42 / 16 | |
| 1.0.596 | 42 / 16 | |
| 1.0.595 | 42 / 16 | |
| 1.0.594 | 42 / 16 | |
| 1.0.593 | 43 / 16 | |
| 1.0.592 | 43 / 16 | |
| 1.0.591 | 43 / 16 | |
| 1.0.590 | 43 / 16 | |
| 1.0.589 | 43 / 16 | |
| 1.0.588 | 43 / 16 | |
| 1.0.587 | 43 / 16 | |
| 1.0.586 | 43 / 16 | |
| 1.0.585 | 43 / 16 | |
| 1.0.584 | 43 / 16 | |
| 1.0.583 | 43 / 16 | |
| 1.0.582 | 43 / 16 | |
| 1.0.581 | 43 / 16 | |
| 1.0.580 | 43 / 16 | |
| 1.0.579 | 43 / 16 | |
| 1.0.578 | 43 / 16 | |
| 1.0.577 | 43 / 16 | |
| 1.0.576 | 43 / 16 | |
| 1.0.575 | 43 / 16 | |
| 1.0.574 | 43 / 16 | |
| 1.0.573 | 43 / 16 | |
| 1.0.572 | 43 / 16 | |
| 1.0.571 | 43 / 16 | |
| 1.0.570 | 43 / 16 | |
| 1.0.569 | 43 / 16 | |
| 1.0.568 | 43 / 16 | |
| 1.0.567 | 43 / 16 | |
| 1.0.566 | 43 / 16 | |
| 1.0.565 | 43 / 16 | |
| 1.0.564 | 43 / 16 | |
| 1.0.563 | 43 / 16 | |
| 1.0.562 | 43 / 16 | |
| 1.0.561 | 43 / 16 | |
| 1.0.560 | 43 / 16 | |
| 1.0.559 | 43 / 16 | |
| 1.0.558 | 43 / 16 | |
| 1.0.557 | 43 / 16 | |
| 1.0.556 | 43 / 16 | |
| 1.0.555 | 43 / 16 | |
| 1.0.554 | 43 / 16 | |
| 1.0.553 | 43 / 16 |
v1.0.723
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.722
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.705
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.649
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.648
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.647
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.646
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.645
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.644
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.643
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.642
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.641
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.640
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.639
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.638
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.637
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.636
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.635
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.634
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.633
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.632
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.631
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.630
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.629
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.628
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.627
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.626
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.625
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.624
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.623
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.622
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.621
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.620
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.619
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.618
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.617
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.616
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.615
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.614
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.613
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.612
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.611
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.609
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.608
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.607
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.606
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.605
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.604
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.603
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.602
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.601
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.600
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.599
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.598
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.597
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.596
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.595
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.594
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.593
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.592
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.591
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.590
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.589
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.588
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.587
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.586
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.585
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.584
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.583
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.582
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.581
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.580
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.579
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.578
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.577
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.576
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.575
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.574
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.573
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.572
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.571
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.570
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.569
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.568
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.567
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.566
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.565
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.564
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.563
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.562
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.561
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.560
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.559
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.558
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.557
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.556
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.555
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.554
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.553
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.