nodeunit-x
Easy unit testing for node.js and the browser.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in deps/json2.js is the classic Crockford JSON2 polyfill — a well-known, decades-old pattern for JSON parsing. Stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() in nodeunit.js loads user-specified test files — core functionality of a test runner, not a supply-chain risk. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in JUnit reporter solely to run mkdir -p for output directory creation. Benign and expected for this test framework. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn('mkdir', ['-p', path]) in JUnit reporter creates output directories. Stable, benign use for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 2 / 2 | |
| 0.15.0 | 2 / 2 | |
| 0.14.0 | 2 / 2 | |
| 0.13.0 | 2 / 2 | |
| 0.12.2 | 2 / 2 | |
| 0.12.1 | 2 / 2 | |
| 0.12.0 | 2 / 2 |
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.