docpad-plugin-ghpages MIT 18 versions

docpad-plugin-ghpages

npm Repository Homepage

Deploy to Github Pages easily via `docpad deploy-ghpages`

18

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

baluptonbevrymekizurobloachstormpooper

Keywords

coffeescriptdocpaddocpad-deployerdocpad-pluginghpagesgithubgithub-pagesnode

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): balupton→bevryme is a documented Bevry org account consolidation; package.json, repo URL, and author field all confirm same organization. Not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): bevryme and stormpooper are Bevry org accounts; consistent with the same organizational transition as the publisher change. Legitimate maintainer addition.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
2.8.0	5 / 7	2020-08-05
2.7.0	5 / 6	2018-06-25
2.6.1	4 / 4	2017-04-19
2.6.0	4 / 4	2017-04-18
2.5.0	4 / 4	2017-04-18
2.4.4	4 / 4	2015-02-18
2.4.3	4 / 4	2014-01-24
2.4.2	4 / 4	2014-01-10
2.4.1	2 / 3	2013-12-12
2.4.0	2 / 3	2013-09-17
2.3.0	2 / 2	2013-07-28
2.2.0	2 / 2	2013-07-08
2.1.2	2 / 2	2013-06-28
2.1.0	2 / 2	2013-06-24
2.0.3	1 / 2	2013-06-14
2.0.2	1 / 1	2013-04-05
2.0.1	1 / 1	2013-04-01
2.0.0	1 / 1	2013-03-06

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

2 findings

HIGH Publisher changed: balupton → bevryme (on 2017-04-18) provenance

This version was published by a different npm account than previous versions on 2017-04-18. 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.

v2.5.0

2 findings

HIGH Publisher changed: balupton → bevryme (on 2017-04-18) provenance

This version was published by a different npm account than previous versions on 2017-04-18. 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.

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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