@mintlify/components
Mintlify open-source UI components
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Mintlify org package; dormancy reflects scoped package cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@base-ui-components/react | AI (dependencies): @base-ui-components/react is the official MUI Base UI library; legitimate and well-known dependency. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:mermaid | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:hast | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@headlessui/react | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@shikijs/transformers | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@sindresorhus/slugify | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:color | AI (phantom-deps): Bundled component library; deps consumed at build time, not directly imported in source. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.17 | 14 / 29 | |
| 0.4.14 | 3 / 24 | |
| 0.4.13 | 3 / 24 | |
| 0.4.11 | 3 / 24 | |
| 0.4.10 | 3 / 24 | |
| 0.4.9 | 3 / 24 | |
| 0.4.8 | 3 / 24 | |
| 0.4.7 | 2 / 24 | |
| 0.4.6 | 2 / 24 | |
| 0.4.5 | 1 / 23 | |
| 0.4.4 | 1 / 23 | |
| 0.4.3 | 1 / 23 | |
| 0.4.2 | 1 / 23 | |
| 0.4.1 | 1 / 23 | |
| 0.4.0 | 1 / 23 |
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.