@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 428)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.0.552 | 43 / 16 | |
| 1.0.551 | 43 / 16 | |
| 1.0.550 | 43 / 16 | |
| 1.0.549 | 43 / 16 | |
| 1.0.548 | 43 / 16 | |
| 1.0.547 | 41 / 16 | |
| 1.0.546 | 41 / 16 | |
| 1.0.545 | 41 / 16 | |
| 1.0.544 | 41 / 16 | |
| 1.0.543 | 41 / 16 | |
| 1.0.542 | 41 / 16 | |
| 1.0.541 | 41 / 16 | |
| 1.0.540 | 41 / 16 | |
| 1.0.539 | 41 / 16 | |
| 1.0.538 | 41 / 16 | |
| 1.0.537 | 41 / 16 | |
| 1.0.536 | 41 / 16 | |
| 1.0.535 | 41 / 16 | |
| 1.0.534 | 41 / 16 | |
| 1.0.533 | 41 / 16 | |
| 1.0.532 | 41 / 16 | |
| 1.0.531 | 41 / 16 | |
| 1.0.530 | 41 / 16 | |
| 1.0.529 | 41 / 16 | |
| 1.0.528 | 41 / 16 | |
| 1.0.527 | 41 / 16 | |
| 1.0.526 | 41 / 16 | |
| 1.0.525 | 41 / 16 | |
| 1.0.524 | 41 / 16 | |
| 1.0.523 | 41 / 16 | |
| 1.0.522 | 41 / 16 | |
| 1.0.521 | 41 / 16 | |
| 1.0.520 | 41 / 16 | |
| 1.0.519 | 41 / 16 | |
| 1.0.518 | 41 / 16 | |
| 1.0.517 | 41 / 16 | |
| 1.0.516 | 41 / 16 | |
| 1.0.515 | 41 / 16 | |
| 1.0.514 | 41 / 16 | |
| 1.0.513 | 41 / 16 | |
| 1.0.512 | 41 / 16 | |
| 1.0.511 | 41 / 16 | |
| 1.0.510 | 41 / 16 | |
| 1.0.509 | 41 / 16 | |
| 1.0.508 | 41 / 16 | |
| 1.0.507 | 41 / 16 | |
| 1.0.506 | 41 / 16 | |
| 1.0.505 | 41 / 16 | |
| 1.0.504 | 41 / 16 | |
| 1.0.503 | 41 / 16 | |
| 1.0.502 | 41 / 16 | |
| 1.0.501 | 41 / 16 | |
| 1.0.500 | 41 / 16 | |
| 1.0.499 | 41 / 16 | |
| 1.0.498 | 41 / 16 | |
| 1.0.497 | 41 / 16 | |
| 1.0.496 | 41 / 16 | |
| 1.0.495 | 41 / 16 | |
| 1.0.494 | 41 / 16 | |
| 1.0.493 | 41 / 16 | |
| 1.0.492 | 41 / 16 | |
| 1.0.491 | 41 / 16 | |
| 1.0.490 | 41 / 16 | |
| 1.0.489 | 41 / 16 | |
| 1.0.488 | 41 / 16 | |
| 1.0.487 | 41 / 16 |
v1.0.586
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.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.
v1.0.552
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.551
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.550
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.549
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.548
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.547
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.546
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.545
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.544
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.543
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.542
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.541
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.540
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.539
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.538
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.537
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.536
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.535
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.534
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.533
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.532
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.531
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.530
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.529
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.528
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.527
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.526
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.525
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.524
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.523
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.522
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.521
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.520
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.519
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.518
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.517
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.516
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.515
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.514
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.513
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.512
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.511
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.510
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.509
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.508
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.507
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.506
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.505
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.504
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.503
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.502
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.501
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.500
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.499
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.498
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.497
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.496
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.495
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.494
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.493
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.492
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.491
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.490
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.489
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.488
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.487
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.