@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 93 of 394)
| Version | Deps | Published |
|---|---|---|
| 1.0.452 | 36 / 16 | |
| 1.0.451 | 36 / 16 | |
| 1.0.450 | 36 / 16 | |
| 1.0.449 | 36 / 16 | |
| 1.0.448 | 36 / 16 | |
| 1.0.447 | 36 / 16 | |
| 1.0.446 | 36 / 16 | |
| 1.0.445 | 36 / 16 | |
| 1.0.444 | 36 / 16 | |
| 1.0.443 | 36 / 16 | |
| 1.0.442 | 36 / 16 | |
| 1.0.441 | 36 / 16 | |
| 1.0.440 | 36 / 16 | |
| 1.0.439 | 36 / 16 | |
| 1.0.438 | 36 / 16 | |
| 1.0.437 | 36 / 16 | |
| 1.0.436 | 36 / 16 | |
| 1.0.435 | 36 / 16 | |
| 1.0.434 | 36 / 16 | |
| 1.0.433 | 36 / 16 | |
| 1.0.432 | 36 / 16 | |
| 1.0.431 | 36 / 16 | |
| 1.0.430 | 36 / 16 | |
| 1.0.429 | 36 / 16 | |
| 1.0.428 | 36 / 16 | |
| 1.0.427 | 36 / 16 | |
| 1.0.426 | 36 / 16 | |
| 1.0.425 | 35 / 16 | |
| 1.0.424 | 35 / 16 | |
| 1.0.423 | 35 / 16 | |
| 1.0.422 | 35 / 16 | |
| 1.0.421 | 35 / 16 | |
| 1.0.420 | 35 / 16 | |
| 1.0.419 | 35 / 16 | |
| 1.0.418 | 35 / 16 | |
| 1.0.417 | 35 / 16 | |
| 1.0.416 | 35 / 16 | |
| 1.0.415 | 35 / 16 | |
| 1.0.414 | 35 / 16 | |
| 1.0.413 | 35 / 16 | |
| 1.0.412 | 35 / 16 | |
| 1.0.411 | 35 / 16 | |
| 1.0.410 | 35 / 16 | |
| 1.0.409 | 35 / 16 | |
| 1.0.408 | 35 / 16 | |
| 1.0.407 | 35 / 16 | |
| 1.0.406 | 35 / 16 | |
| 1.0.405 | 35 / 16 | |
| 1.0.404 | 35 / 16 | |
| 1.0.403 | 35 / 16 | |
| 1.0.402 | 35 / 16 | |
| 1.0.401 | 35 / 16 | |
| 1.0.400 | 35 / 16 | |
| 1.0.399 | 35 / 16 | |
| 1.0.398 | 35 / 16 | |
| 1.0.397 | 35 / 16 | |
| 1.0.396 | 35 / 16 | |
| 1.0.395 | 35 / 16 | |
| 1.0.394 | 35 / 16 | |
| 1.0.393 | 35 / 16 | |
| 1.0.392 | 35 / 16 | |
| 1.0.391 | 35 / 16 | |
| 1.0.390 | 35 / 16 | |
| 1.0.389 | 35 / 16 | |
| 1.0.388 | 35 / 16 | |
| 1.0.387 | 35 / 16 | |
| 1.0.386 | 35 / 16 | |
| 1.0.385 | 35 / 16 | |
| 1.0.384 | 35 / 16 | |
| 1.0.383 | 35 / 16 | |
| 1.0.382 | 36 / 16 | |
| 1.0.381 | 36 / 16 | |
| 1.0.380 | 36 / 16 | |
| 1.0.379 | 36 / 16 | |
| 1.0.378 | 36 / 16 | |
| 1.0.377 | 36 / 16 | |
| 1.0.376 | 36 / 16 | |
| 1.0.375 | 36 / 16 | |
| 1.0.374 | 36 / 16 | |
| 1.0.373 | 36 / 16 | |
| 1.0.372 | 36 / 16 | |
| 1.0.371 | 36 / 16 | |
| 1.0.370 | 36 / 16 | |
| 1.0.369 | 36 / 16 | |
| 1.0.368 | 36 / 16 | |
| 1.0.367 | 36 / 16 | |
| 1.0.366 | 36 / 16 | |
| 1.0.365 | 36 / 16 | |
| 1.0.364 | 36 / 16 | |
| 1.0.363 | 35 / 16 | |
| 1.0.362 | 35 / 16 | |
| 1.0.361 | 35 / 16 | |
| 1.0.360 | 35 / 16 |
v1.0.452
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.451
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.450
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.449
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.448
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.447
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.446
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.445
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.444
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.443
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.442
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.441
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.440
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.439
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.438
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.437
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.436
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.435
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.434
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.433
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.432
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.431
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.430
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.429
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.428
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.427
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.426
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.425
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.424
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.423
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.422
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.421
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.420
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.419
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.418
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.417
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.416
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.415
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.414
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.413
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.412
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.411
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.410
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.409
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.408
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.407
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.406
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.405
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.404
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.403
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.402
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.401
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.400
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.399
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.398
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.397
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.396
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.395
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.394
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.393
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.392
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.391
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.390
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.389
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.388
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.387
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.386
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.385
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.384
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.383
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.382
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.381
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.380
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.379
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.378
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.377
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.376
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.375
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.374
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.373
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.372
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.371
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.370
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.369
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.368
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.367
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.366
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.365
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.364
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.363
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.362
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.361
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.360
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.