docpad-plugin-eco
Adds support for the Eco templating engine to DocPad.
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 robloach to bevryme reflects legitimate transfer to Bevry org, which is the canonical author of this package per package.json and repository URL. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (bevryme, kizu, stormpooper) are Bevry org members; consistent with the package's stated authorship and repository ownership. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 2 / 10 | |
| 2.7.0 | 2 / 10 | |
| 2.6.0 | 2 / 10 | |
| 2.5.0 | 2 / 10 | |
| 2.3.0 | 2 / 6 | |
| 2.2.1 | 1 / 4 | |
| 2.2.0 | 1 / 4 | |
| 2.1.0 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.0.0 | 1 / 0 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsThis version was published by a different npm account than previous versions on 2018-06-25. 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.
v2.2.1
2 findingsThis version was published by a different npm account than previous versions on 2017-04-20. 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.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2017-04-16. 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.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2014-09-25. 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.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.