@mintlify/scraping
Scrape documentation frameworks to Mintlify docs
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 |
|---|---|---|---|---|
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a legitimate source-available license used intentionally by Mintlify, Inc. Not a security concern. | ai | |
| dependencies | unvetted-dep:@mintlify/openapi-parser | AI (dependencies): Same-org dependency (@mintlify scope); consistent with Mintlify's internal package ecosystem and the package's documented purpose. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance attestation is common and not a risk signal for this established package with 225k weekly downloads. | ai | |
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): remark-parse is used indirectly via the unified/remark pipeline; phantom detection is a false positive for this package's architecture. | ai | |
| phantom-deps | phantom-dep:@mintlify/openapi-parser | AI (phantom-deps): Same-org dependency; phantom detection is a false positive for @mintlify scoped packages used within the Mintlify ecosystem. | ai |
Versions (showing 37 of 338)
| Version | Deps | Published |
|---|---|---|
| 4.0.251 | 17 / 19 | |
| 4.0.250 | 17 / 19 | |
| 4.0.249 | 17 / 19 | |
| 4.0.248 | 17 / 19 | |
| 4.0.247 | 17 / 19 | |
| 4.0.246 | 17 / 19 | |
| 4.0.245 | 17 / 19 | |
| 4.0.244 | 17 / 19 | |
| 4.0.243 | 17 / 19 | |
| 4.0.242 | 17 / 19 | |
| 4.0.241 | 17 / 19 | |
| 4.0.240 | 17 / 19 | |
| 4.0.239 | 17 / 19 | |
| 4.0.238 | 17 / 19 | |
| 4.0.237 | 17 / 19 | |
| 4.0.236 | 17 / 19 | |
| 4.0.235 | 17 / 19 | |
| 4.0.234 | 17 / 19 | |
| 4.0.233 | 17 / 19 | |
| 4.0.232 | 17 / 19 | |
| 4.0.231 | 17 / 19 | |
| 4.0.230 | 17 / 19 | |
| 4.0.229 | 17 / 19 | |
| 4.0.228 | 17 / 19 | |
| 4.0.227 | 17 / 19 | |
| 4.0.226 | 17 / 19 | |
| 4.0.225 | 17 / 19 | |
| 4.0.224 | 17 / 19 | |
| 4.0.223 | 17 / 19 | |
| 4.0.222 | 17 / 19 | |
| 4.0.221 | 17 / 19 | |
| 4.0.220 | 17 / 19 | |
| 4.0.219 | 17 / 19 | |
| 4.0.218 | 17 / 19 | |
| 4.0.217 | 17 / 19 | |
| 4.0.216 | 17 / 19 | |
| 4.0.215 | 17 / 19 |
v4.0.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.249
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.241
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.238
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.236
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.235
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.234
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.233
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.232
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.231
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.230
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.229
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.228
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.227
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.226
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.225
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.224
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.223
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.222
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.221
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.220
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.219
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.218
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.217
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.216
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.