← Home

git-cliff

npm Repository Homepage

A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️

6
Versions
MIT OR Apache-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

orhun

Keywords

git-cliffgitchangelogchange logCHANGELOG.mdcommit messagescommitschangesunreleasedhistorywhat's newchange setconventionalcommits.orgconventionalconventional-commitconventional-changelogreleasesrelease notesgit-changelogversioningsemverdistributionsemanticsemantic versioningparserchangelog-generatorgeneratorkeepachangelogkeep-a-changelogcommitautomationrust

Versions (showing 6 of 6)

Version Deps Published
2.13.1 1 / 9
2.12.0 1 / 9
2.11.0 1 / 9
2.10.1 1 / 9
2.10.0 1 / 9
2.9.1 1 / 9

v2.13.1

1 finding
LOW No provenance attestation provenance

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

v2.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.10.1

1 finding
LOW No provenance attestation provenance

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

v2.10.0

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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