cz-customizable
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads user-specified config file path; core feature of a customizable config adapter. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in standalone CLI to invoke git; expected for a commitizen adapter. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 7.5.4 | 6 / 13 | |
| 7.5.3 | 6 / 13 | |
| 7.5.2 | 6 / 13 | |
| 7.5.1 | 6 / 13 | |
| 7.5.0 | 6 / 13 | |
| 7.4.0 | 6 / 13 | |
| 7.3.0 | 6 / 13 | |
| 7.2.1 | 6 / 13 | |
| 7.2.0 | 6 / 13 | |
| 7.1.0 | 6 / 13 |
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.