@commitlint/resolve-extends
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): require() is gated to .json files only — a standard pattern for loading JSON config files. Not arbitrary module loading; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync is used solely to run 'npm config get cache' for npm cache directory resolution — a read-only, benign operation appropriate for this config-resolution package. | ai | |
| provenance | no-provenance | AI (provenance): Established commitlint monorepo package; lack of Sigstore provenance is common and not a risk signal for this well-known project. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 5 / 2 | |
| 21.0.0 | 5 / 1 | |
| 20.5.3 | 6 / 1 | |
| 20.5.2 | 6 / 2 | |
| 20.5.0 | 6 / 2 | |
| 20.4.4 | 6 / 2 | |
| 20.4.3 | 6 / 2 | |
| 20.4.0 | 6 / 2 | |
| 20.3.1 | 6 / 2 | |
| 20.2.0 | 6 / 2 | |
| 20.1.0 | 6 / 2 | |
| 20.0.0 | 6 / 2 |
v21.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.