@rosen-clients/ergo-node
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 | obfuscated-file:dist/types/blockHeader.js | AI (source-diff): Long lines are base64 sourcemap comments in compiled TS output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/blockHeaderWithoutPow.js | AI (source-diff): Same pattern: base64 sourcemap in compiled TS dist file. | ai | |
| source-diff | obfuscated-file:dist/types/candidateBlock.js | AI (source-diff): Same pattern: base64 sourcemap in compiled TS dist file. | ai | |
| source-diff | large-new-source-files | AI (source-diff): API client library with orval-generated files; large file count is expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here. | ai |
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.