← Home

@mintlify/scraping

Scrape documentation frameworks to Mintlify docs

3
Versions
Elastic-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

dks333hanminthahnbeeshouchem-mintlifykathrynmintlifykylefinkenian-mintlifydenssumesh

Keywords

mintlifymintscraping

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 3 of 304)

Version Deps Published
4.0.217 17 / 19
4.0.216 17 / 19
4.0.215 17 / 19

v4.0.217

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.