git-log-parser MIT 4 versions

git-log-parser

npm Repository Homepage

git-log-parser

Versions

MIT

License

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.

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): git-log-parser's core function is spawning the git binary via child_process.spawn; this is expected and benign for this package across all versions.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established package published long before Sigstore provenance was available on npm; absence is expected and not a risk signal here.	ai	2026/04/24

Versions (showing 4 of 4)

Version	Deps	Published
1.2.1	6 / 2	2024-07-01
1.2.0	6 / 2	2015-11-05
1.1.0	6 / 2	2015-07-08
1.0.0	6 / 2	2014-11-23

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.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.