nodent-compiler
NoDent - Asynchronous Javascript language extensions
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:output.js | AI (source-diff): output.js is a JavaScript AST-to-code generator (derived from Astring). The 'network call' is require('source-map') and 'code execution' is AST traversal/code generation — both are core compiler functionality, not malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large file additions reflect a legitimate refactor extracting transform logic into the companion nodent-transform package; consistent with the package's compiler nature. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.2.13 | 4 / 1 | |
| 3.2.11 | 4 / 1 | |
| 3.2.10 | 4 / 1 | |
| 3.2.9 | 4 / 1 | |
| 3.2.6 | 4 / 1 | |
| 3.2.5 | 4 / 1 | |
| 3.2.4 | 4 / 1 | |
| 3.2.2 | 4 / 1 | |
| 3.2.1 | 4 / 1 | |
| 3.2.0 | 4 / 1 | |
| 3.1.8 | 3 / 0 | |
| 3.1.7 | 3 / 0 | |
| 3.1.6 | 3 / 0 | |
| 3.1.5 | 3 / 0 | |
| 3.1.4 | 3 / 0 | |
| 3.1.3 | 3 / 0 | |
| 3.1.2 | 3 / 0 | |
| 3.1.0 | 3 / 0 |
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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.4
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.