@neuraiproject/neurai-sign-transaction
Signs a Neurai transaction
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:dist/browser.js | AI (source-diff): Rollup browser bundle with standard polyfills; no actual dropper/loader behavior in the code. | ai | |
| phantom-deps | phantom-dep:bitcoinjs-lib | AI (phantom-deps): bitcoinjs-lib is a peer/transitive dep used via config; phantom-dep false positive for this package. | ai | |
| source-diff | net-exec-file:dist/NeuraiSignTransaction.global.js | AI (source-diff): Rollup global bundle with standard polyfills; no actual dropper/loader behavior in the code. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for standard Bitcoin transaction hash byte-reversal in bitcoinjs-lib; not obfuscation. | ai | |
| phantom-deps | phantom-dep:ecpair | AI (phantom-deps): ecpair is a real runtime dep pinned in overrides; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@neuraiproject/neurai-scripts | AI (phantom-deps): Same-org build tooling dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@bitcoinerlab/secp256k1 | AI (phantom-deps): Listed as runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 6 / 11 | |
| 2.1.1 | 6 / 11 | |
| 2.1.0 | 6 / 11 | |
| 2.0.0 | 6 / 11 | |
| 1.4.0 | 6 / 11 | |
| 1.3.0 | 6 / 11 | |
| 1.2.2 | 5 / 11 | |
| 1.2.1 | 5 / 11 | |
| 1.2.0 | 5 / 11 | |
| 1.1.3 | 4 / 7 | |
| 1.1.2 | 3 / 6 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v2.1.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v2.0.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.4.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.3.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.2.2
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.2.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.2.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly 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.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.