consolidate MIT 30 versions

consolidate

npm Repository Homepage

Modern and maintained fork of the template engine consolidation library. Maintained and supported by Forward Email <https://forwardemail.net>, the 100% open-source and privacy-focused email service.

30

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

niftylettucetjholowaychukdoowbtitanism

Keywords

enginetemplateview

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition within ladjs org (niftylettuce/titanism are both ladjs maintainers). Repo confirms ladjs/consolidate ownership.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): titanism is a known ladjs org member; legitimate maintainer transition for this package.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): bridgear removal is part of the legitimate ladjs org maintainer transition.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core design of consolidate — it loads user-chosen template engines by name. Inherent to the library.	ai	2026/04/24

Versions (showing 30 of 30)

Version	Deps	Published
1.0.4	0 / 59	2024-07-10
1.0.3	0 / 59	2023-09-30
1.0.1	0 / 58	2023-06-09
1.0.0	0 / 58	2023-06-09
0.16.0	1 / 59	2020-09-08
0.15.1	1 / 55	2018-03-20
0.15.0	1 / 55	2017-11-01
0.14.5	1 / 49	2016-11-17
0.14.4	1 / 48	2016-11-11
0.14.2	1 / 46	2016-11-11
0.14.1	1 / 40	2016-04-28
0.14.0	1 / 39	2016-01-24
0.13.1	1 / 36	2015-05-26
0.13.0	1 / 36	2015-05-26
0.12.1	0 / 36	2015-03-29
0.12.0	0 / 36	2015-03-29
0.11.0	0 / 34	2015-02-09
0.10.0	0 / 31	2013-11-23
0.9.1	0 / 28	2013-04-30
0.9.0	0 / 28	2013-03-28
0.8.0	0 / 26	2013-01-24
0.7.0	0 / 25	2012-12-28
0.6.0	0 / 24	2012-12-22
0.5.0	0 / 24	2012-10-29
0.4.0	0 / 21	2012-07-30
0.3.1	0 / 18	2012-06-28
0.3.0	0 / 17	2012-04-18
0.2.0	0 / 16	2012-04-04
0.1.0	0 / 14	2012-01-04
0.0.1	0 / 10	2011-11-20

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: niftylettuce → titanism (on 2023-06-09) provenance

This version was published by a different npm account than previous versions on 2023-06-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.16.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 → niftylettuce (on 2020-09-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-08. This could indicate a legitimate maintainer transition or an account compromise.

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.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: niftylettuce → doowb (on 2017-11-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-01. This could indicate a legitimate maintainer transition or an account compromise.

v0.14.5

1 finding

LOW No provenance attestation provenance

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

v0.14.4

1 finding

LOW No provenance attestation provenance

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

v0.14.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 → niftylettuce (on 2016-11-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-11. This could indicate a legitimate maintainer transition or an account compromise.

v0.14.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: bridgear → doowb (on 2016-04-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-28. This could indicate a legitimate maintainer transition or an account compromise.

v0.14.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 → bridgear (on 2016-01-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-01-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.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: tjholowaychuk → doowb (on 2015-02-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

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.