← Home

boil

Boilerplate files, packages, apps, websites etc.

5
Versions
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

75lb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package predates Sigstore provenance; trusted publisher with strong track record. Low risk for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is used to load user-specified Handlebars helper files — intentional and documented behavior for this boilerplate CLI tool, not an arbitrary code execution risk. ai
typosquat typosquat.levenshtein:joi AI (typosquat): 'boil' is a CLI tool for HTML5 Boilerplate, predating joi's popularity by years. The name similarity is coincidental and not a typosquat. ai
bogus-package bogus-package AI (bogus-package): Minimal CLI tool from Node 0.4.x era; tiny payload and empty index.js are expected for a bin-only package. ai

Versions (showing 5 of 5)

Version Deps Published
0.5.0 0 / 2
0.4.1 19 / 1
0.3.0 19 / 1
0.2.9 19 / 1
0.0.1 0 / 0

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.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.

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.9

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.

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