← Home

beautify.hks

npm Repository Homepage

Beautify your javascript with each commit

4
Versions
BSD-2-Clause
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mcwhittemore

Keywords

hookspre-commitbeautificationgitjs-beautify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): postinstall runs 'node config.js' to register the git pre-commit hook — core functionality of this package, stable across versions, not a malicious payload. ai
semgrep semgrep:child-process-import AI (semgrep): child_process is used to interact with git and run beautification commands, which is expected behavior for a git hook runner tool. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this established package. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.5 5 / 1
0.0.3 5 / 1
0.0.2 4 / 1
0.0.1 2 / 1

v0.0.5

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

Script: node config.js

LOW No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

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

v0.0.1

1 finding
INFO No provenance attestation provenance

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