handlebars-helpers MIT 34 versions

handlebars-helpers

npm Repository Homepage

More than 130 Handlebars helpers in ~20 categories. Helpers can be used with Assemble, Generate, Verb, Ghost, gulp-handlebars, grunt-handlebars, consolidate, or any node.js/Handlebars project.

34

Versions

MIT

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

spacedawwwgjonschlinkertdoowb

Keywords

arrayassemblecollectioncomparisondatehandlebarshelperhelpershtmli18ninflectionlogloggingmarkdownmathnumberobjectpathrepeatstringtemplatetimeurlutilutility

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:helper-repeat	AI (phantom-deps): Config-only reference, long-standing dependency.	ai	2026/07/20
phantom-deps	phantom-dep:helper-prettify	AI (phantom-deps): Config-only reference, long-standing dependency.	ai	2026/07/20
phantom-deps	phantom-dep:js-yaml	AI (phantom-deps): Used indirectly via config, stable false positive.	ai	2026/07/20
semgrep	semgrep:dynamic-require	AI (semgrep): Helper-file plugin loader pattern, not arbitrary remote code.	ai	2026/07/20
phantom-deps	phantom-dep:mime	AI (phantom-deps): Used indirectly via config, stable false positive.	ai	2026/07/20
phantom-deps	phantom-dep:markdown-utils	AI (phantom-deps): Config-referenced, not a real risk.	ai	2026/07/20
provenance	publisher-changed-stale	AI (provenance): Stale historical change, stable for years, not a takeover indicator.	ai	2026/07/20
phantom-deps	phantom-dep:to-file	AI (phantom-deps): Config-referenced, not a real risk.	ai	2026/07/20
phantom-deps	phantom-dep:repo-utils	AI (phantom-deps): Config-referenced, not a real risk.	ai	2026/07/20
phantom-deps	phantom-dep:code-context	AI (phantom-deps): Config-referenced, not a real risk.	ai	2026/07/20

Versions (showing 34 of 34)

Version	Deps	Published
0.10.0	28 / 20	2017-11-17
0.9.8	28 / 20	2017-08-31
0.9.7	28 / 20	2017-08-22
0.9.6	28 / 20	2017-07-28
0.9.5	27 / 20	2017-07-25
0.9.4	27 / 20	2017-07-20
0.9.3	27 / 20	2017-07-10
0.9.2	27 / 20	2017-07-06
0.9.1	27 / 20	2017-07-04
0.9.0	27 / 20	2017-07-04
0.8.4	29 / 21	2017-07-03
0.8.3	29 / 21	2017-07-03
0.8.2	29 / 21	2017-03-31
0.8.1	29 / 21	2017-03-30
0.8.0	29 / 21	2017-01-25
0.7.7	29 / 21	2017-01-08
0.7.6	29 / 19	2017-01-08
0.7.5	28 / 20	2016-08-17
0.7.4	28 / 17	2016-08-17
0.7.3	32 / 15	2016-07-15
0.7.2	32 / 15	2016-07-15
0.7.1	32 / 15	2016-07-15
0.7.0	32 / 15	2016-07-15
0.6.2	32 / 15	2016-07-07
0.6.1	28 / 15	2016-05-18
0.6.0	29 / 15	2016-05-13
0.3.16	15 / 11	2013-10-22
0.3.14	15 / 11	2013-10-16
0.3.5	11 / 11	2013-09-16
0.3.4	9 / 13	2013-09-05
0.3.3	9 / 13	2013-09-03
0.3.1	8 / 13	2013-08-02
0.2.9	8 / 12	2013-07-24
0.2.6	7 / 15	2013-06-30

v0.9.8

1 finding

LOW No provenance attestation provenance

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

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2017-07-28, known maintainer) provenance

This version was published by a different npm account (jonschlinkert) than the most recent previously approved version (doowb) on 2017-07-28, but jonschlinkert is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.5

1 finding

LOW No provenance attestation provenance

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

v0.9.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2017-07-20, known maintainer) provenance

This version was published by a different npm account (jonschlinkert) than the most recent previously approved version (doowb) on 2017-07-20, but jonschlinkert is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2017-07-10, known maintainer) provenance

This version was published by a different npm account (doowb) than the most recent previously approved version (jonschlinkert) on 2017-07-10, but doowb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2017-07-06, known maintainer) provenance

This version was published by a different npm account (doowb) than the most recent previously approved version (jonschlinkert) on 2017-07-06, but doowb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2017-07-04, known maintainer) provenance

This version was published by a different npm account (jonschlinkert) than the most recent previously approved version (doowb) on 2017-07-04, but jonschlinkert is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2017-07-04, known maintainer) provenance

This version was published by a different npm account (jonschlinkert) than the most recent previously approved version (doowb) on 2017-07-04, but jonschlinkert is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2017-03-30, known maintainer) provenance

This version was published by a different npm account (doowb) than the most recent previously approved version (jonschlinkert) on 2017-03-30, but doowb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.7

1 finding

LOW No provenance attestation provenance

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

v0.7.6

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

2 findings

MEDIUM Publisher changed: jonschlinkert → spacedawwwg (on 2016-07-15, unremoved on npm for 3657d) provenance

This version was published by a different npm account (spacedawwwg) than the most recent previously approved version (jonschlinkert) on 2016-07-15. It has since remained available on npm for 3657 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.2

2 findings

MEDIUM Publisher changed: jonschlinkert → spacedawwwg (on 2016-07-15, unremoved on npm for 3657d) provenance

This version was published by a different npm account (spacedawwwg) than the most recent previously approved version (jonschlinkert) on 2016-07-15. It has since remained available on npm for 3657 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.1

2 findings

MEDIUM Publisher changed: jonschlinkert → spacedawwwg (on 2016-07-15, unremoved on npm for 3657d) provenance

This version was published by a different npm account (spacedawwwg) than the most recent previously approved version (jonschlinkert) on 2016-07-15. It has since remained available on npm for 3657 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.0

2 findings

MEDIUM Publisher changed: doowb → spacedawwwg (on 2016-07-15, unremoved on npm for 3657d) provenance

This version was published by a different npm account (spacedawwwg) than the most recent previously approved version (doowb) on 2016-07-15. It has since remained available on npm for 3657 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2016-07-07, known maintainer) provenance

This version was published by a different npm account (jonschlinkert) than the most recent previously approved version (doowb) on 2016-07-07, but jonschlinkert is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.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.6.0

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.16

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.14

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

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

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.3

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.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.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.2.6

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.