zombie
Insanely fast, full-stack, headless browser testing using Node.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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): forbeslindesay is a highly reputable npm publisher (1709 approved packages, active since 2013). The maintainer transition from mdlavin occurred in 2017 and is a historical, legitimate handoff. | ai | |
| provenance | publisher-changed | AI (provenance): assaf is the original package author (assaf/zombie on GitHub); djanowski was a contributor. The transfer back to the original author is legitimate and consistent with package metadata. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require is `require(__dirname + '/../package.json').version` — a hardcoded path to read the package's own version. Not a security risk; stable pattern for this package. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 6.1.3 | 12 / 21 | |
| 6.1.2 | 12 / 21 | |
| 6.1.1 | 12 / 19 | |
| 6.1.0 | 12 / 19 | |
| 6.0.0 | 12 / 19 | |
| 5.0.7 | 12 / 19 | |
| 5.0.5 | 12 / 19 | |
| 5.0.3 | 12 / 19 | |
| 5.0.2 | 12 / 19 | |
| 5.0.1 | 12 / 19 | |
| 5.0.0 | 12 / 19 | |
| 4.3.0 | 12 / 19 | |
| 4.2.1 | 12 / 19 | |
| 4.2.0 | 12 / 19 | |
| 4.1.0 | 12 / 19 | |
| 4.0.13 | 12 / 19 | |
| 4.0.12 | 12 / 19 | |
| 4.0.11 | 12 / 19 | |
| 4.0.10 | 12 / 19 | |
| 4.0.9 | 12 / 19 | |
| 4.0.8 | 12 / 18 | |
| 4.0.7 | 12 / 18 | |
| 4.0.6 | 12 / 18 | |
| 4.0.5 | 12 / 18 | |
| 4.0.4 | 12 / 18 | |
| 4.0.3 | 12 / 18 | |
| 4.0.2 | 12 / 18 | |
| 4.0.1 | 12 / 18 | |
| 4.0.0 | 12 / 18 | |
| 3.1.1 | 11 / 18 | |
| 3.1.0 | 11 / 16 | |
| 3.0.15 | 11 / 16 | |
| 2.5.1 | 11 / 16 | |
| 2.5.0 | 11 / 16 | |
| 2.4.0 | 10 / 16 | |
| 2.3.2 | 10 / 16 | |
| 2.3.1 | 10 / 16 | |
| 2.3.0 | 10 / 16 | |
| 2.2.1 | 10 / 17 | |
| 2.2.0 | 10 / 17 | |
| 2.1.1 | 10 / 17 | |
| 2.1.0 | 10 / 17 | |
| 2.0.8 | 10 / 17 | |
| 2.0.7 | 10 / 17 | |
| 2.0.6 | 10 / 17 | |
| 2.0.5 | 10 / 17 | |
| 2.0.4 | 10 / 17 | |
| 2.0.3 | 10 / 17 | |
| 2.0.2 | 10 / 17 | |
| 2.0.1 | 10 / 17 | |
| 2.0.0 | 10 / 17 | |
| 1.4.1 | 9 / 8 | |
| 1.4.0 | 9 / 8 | |
| 1.3.1 | 9 / 7 | |
| 1.3.0 | 9 / 7 | |
| 1.2.0 | 8 / 7 | |
| 1.1.7 | 8 / 7 | |
| 1.1.6 | 8 / 7 | |
| 1.1.5 | 8 / 7 | |
| 1.1.4 | 8 / 7 | |
| 1.1.3 | 8 / 7 | |
| 1.1.2 | 8 / 7 | |
| 1.1.1 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.0 | 8 / 7 | |
| 0.13.14 | 7 / 7 | |
| 0.13.13 | 7 / 7 | |
| 0.13.12 | 7 / 7 | |
| 0.13.11 | 8 / 7 | |
| 0.13.10 | 8 / 7 | |
| 0.13.9 | 8 / 7 | |
| 0.13.8 | 8 / 7 | |
| 0.13.7 | 8 / 7 | |
| 0.13.6 | 8 / 7 | |
| 0.13.4 | 8 / 6 | |
| 0.13.3 | 8 / 6 | |
| 0.13.2 | 8 / 6 | |
| 0.13.1 | 8 / 6 | |
| 0.13.0 | 7 / 6 | |
| 0.12.15 | 4 / 6 | |
| 0.12.14 | 4 / 6 | |
| 0.12.13 | 4 / 6 | |
| 0.12.12 | 4 / 6 | |
| 0.12.11 | 4 / 5 | |
| 0.12.10 | 6 / 5 | |
| 0.12.9 | 6 / 5 | |
| 0.12.8 | 6 / 5 | |
| 0.12.7 | 6 / 5 | |
| 0.12.6 | 6 / 5 | |
| 0.12.5 | 6 / 5 | |
| 0.12.4 | 6 / 5 | |
| 0.12.3 | 6 / 5 | |
| 0.12.2 | 6 / 5 | |
| 0.12.1 | 6 / 5 |
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-04-02. 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.0.7
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-06-26. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.