← Home

@jpp-toolkit/git-hooks

npm Repository Homepage

Git hooks configuration for JS/TS projects.

5
Versions
MIT
License
Yes
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jpapini

Keywords

jppgithooks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Git-hooks setup package; postinstall running node scripts/install.js to configure husky is expected and documented behavior. ai
dependencies unvetted-dep:@jpp-toolkit/utils AI (dependencies): Internal monorepo dependency from the same publisher; consistent with package purpose. ai
dependencies unvetted-dep:@jpp-toolkit/commitlint-config AI (dependencies): Internal monorepo dependency from the same publisher; consistent with package purpose. ai
dependencies unvetted-dep:@jpp-toolkit/lint-staged-config AI (dependencies): Internal monorepo dependency from the same publisher; consistent with package purpose. ai

Versions (showing 5 of 5)

Version Deps Published
0.0.53 7 / 0
0.0.52 7 / 0
0.0.50 7 / 0
0.0.48 7 / 0
0.0.11 7 / 0

v0.0.53

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.52

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.50

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

Script: node scripts/install.js

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.48

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.11

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.