nodent
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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): The install script is a plain echo statement informing users of a breaking change. No code execution, network access, or malicious behavior — stable benign pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:moment | AI (typosquat): nodent is a well-established JS transpiler (4537 days, 195 versions); name similarity to 'moment' is purely coincidental with no brand overlap. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used only to validate host option syntax in a try/catch with result discarded — expected in a JS transpiler context. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() executes compiled output in CLI --exec mode; core functionality of a JS-to-JS compiler. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads named 'covers' (runtime adapters) constrained to the package's own covers/ directory; standard plugin loading in a transpiler. | ai |
Versions (showing 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 3.2.13 | 3 / 0 | |
| 3.2.11 | 3 / 0 | |
| 3.2.10 | 3 / 0 | |
| 3.2.9 | 3 / 0 | |
| 3.2.8 | 3 / 0 | |
| 3.2.7 | 3 / 0 | |
| 3.2.6 | 3 / 0 | |
| 3.2.4 | 3 / 0 | |
| 3.2.2 | 3 / 0 | |
| 3.2.0 | 3 / 0 | |
| 3.1.8 | 3 / 0 | |
| 3.1.7 | 3 / 0 | |
| 3.1.6 | 3 / 0 | |
| 3.1.5 | 3 / 0 | |
| 3.1.3 | 3 / 0 | |
| 3.1.2 | 3 / 0 | |
| 3.1.1 | 3 / 0 | |
| 3.1.0 | 3 / 0 | |
| 3.0.20 | 5 / 0 | |
| 3.0.19 | 5 / 0 | |
| 3.0.18 | 5 / 0 | |
| 3.0.17 | 5 / 0 | |
| 3.0.16 | 5 / 0 | |
| 3.0.14 | 5 / 0 | |
| 3.0.13 | 5 / 0 | |
| 3.0.12 | 5 / 0 | |
| 3.0.11 | 5 / 0 | |
| 3.0.10 | 5 / 0 | |
| 3.0.9 | 5 / 0 | |
| 3.0.8 | 5 / 0 | |
| 3.0.7 | 5 / 0 | |
| 3.0.6 | 5 / 0 | |
| 3.0.5 | 5 / 0 | |
| 3.0.4 | 5 / 0 | |
| 3.0.3 | 5 / 0 | |
| 3.0.2 | 5 / 0 | |
| 3.0.1 | 5 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.6.14 | 4 / 0 | |
| 2.6.13 | 4 / 0 | |
| 2.6.12 | 4 / 0 | |
| 2.6.11 | 4 / 0 | |
| 2.6.10 | 4 / 0 | |
| 2.6.9 | 4 / 0 | |
| 2.6.8 | 4 / 0 | |
| 2.6.7 | 4 / 0 | |
| 2.6.6 | 4 / 0 | |
| 2.6.5 | 4 / 0 | |
| 2.6.4 | 4 / 0 | |
| 2.6.3 | 4 / 0 | |
| 2.6.2 | 4 / 0 |
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.