← Home

pre-commit

npm Repository Homepage

Automatically install pre-commit hooks for your npm modules.

6
Versions
MIT
License
Yes
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

swaagiev13rdeden

Keywords

githooksnpmpre-commitprecommitruntestdevelopment

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): pre-commit is a git hook runner; spawning child processes to execute configured scripts is its core, documented functionality — not a risk for this package. ai
install-scripts install-script:install AI (install-scripts): pre-commit's install script installs git hooks into the consuming project — this is the package's core documented purpose and stable across all versions. ai
semgrep semgrep:dynamic-require AI (semgrep): The dynamic require loads the host project's package.json to read pre-commit config — a necessary and benign pattern for this tool, stable across versions. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.0 2 / 3
1.2.2 3 / 4
1.1.3 2 / 4
1.0.10 1 / 4
1.0.2 1 / 4
1.0.0 1 / 4

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.2.2

2 findings
HIGH Package has 'install' script install-scripts

Script: node install.js

LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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

2 findings
HIGH Publisher changed: V1 → 3rdeden (on 2015-01-30) provenance

This version was published by a different npm account than previous versions on 2015-01-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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