← Home

@rosen-clients/ergo-node

6
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

vorujackzargarzadehm

Keywords

rosenergo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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

Versions (showing 6 of 6)

Version Deps Published
3.2.0 1 / 3
3.1.3 1 / 3
3.1.2 1 / 3
3.1.1 1 / 3
3.1.0 1 / 3
3.0.0 1 / 4

v3.2.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.