vision
Templates rendering plugin support for hapi.js
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from hueniverse to williamswoodruff occurred in Dec 2018 — a known, stable hapijs org transition. Publisher has 25 approved packages and long track record. Not a takeover signal. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is core functionality for a template rendering plugin — it loads user-configured template engines (handlebars, ejs, pug, etc.) at runtime. Expected and benign for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.4.4 | 4 / 16 | |
| 5.4.3 | 4 / 16 | |
| 5.4.2 | 4 / 16 | |
| 5.4.1 | 4 / 16 | |
| 5.4.0 | 4 / 16 | |
| 5.3.3 | 4 / 16 | |
| 5.3.2 | 4 / 16 | |
| 5.3.1 | 4 / 16 | |
| 5.3.0 | 4 / 16 | |
| 5.2.0 | 4 / 15 | |
| 5.1.0 | 4 / 15 | |
| 5.0.0 | 4 / 14 | |
| 4.1.1 | 4 / 14 | |
| 4.1.0 | 4 / 14 | |
| 4.0.1 | 4 / 14 | |
| 4.0.0 | 4 / 13 | |
| 3.0.0 | 4 / 10 | |
| 2.0.1 | 4 / 5 | |
| 2.0.0 | 4 / 5 | |
| 1.2.2 | 3 / 5 | |
| 1.2.1 | 3 / 5 | |
| 1.2.0 | 3 / 5 | |
| 1.1.0 | 3 / 4 | |
| 1.0.3 | 3 / 4 | |
| 1.0.2 | 3 / 4 |
v5.4.4
2 findingsThis version was published by a different npm account than previous versions on 2018-12-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-01. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-29. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.