@ornikar/commitlint-config
📓 commitlint config
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@commitlint/config-lerna-scopes | AI (dependencies): Well-known commitlint ecosystem package; stable false positive for this config package. | ai | |
| phantom-deps | phantom-dep:@commitlint/config-workspace-scopes | AI (phantom-deps): commitlint config deps are referenced declaratively in config files, not imported — phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@commitlint/config-conventional | AI (phantom-deps): Config-only package; deps are referenced in config files, not imported via require/import. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@commitlint/config-lerna-scopes | AI (phantom-deps): Same config-only pattern; referenced in config, not directly imported. Stable FP for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 8.3.0 | 2 / 0 | |
| 8.2.0 | 2 / 0 | |
| 8.1.1 | 2 / 0 | |
| 8.0.1 | 2 / 0 | |
| 8.0.0 | 2 / 0 |
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.