← Home

@hiero-ledger/sdk

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

lfdt-npmrbarkernathan-swirldslabsandrewb1269hg

Keywords

hierohederahashgraphsdktransactions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Buffer.from(str, 'hex') is standard Node.js hex decoding in an encoding utility; not malicious. ai
phantom-deps phantom-dep:bn.js AI (phantom-deps): bn.js is a declared peer dependency; phantom-dep heuristic fires incorrectly here. ai
phantom-deps phantom-dep:debug AI (phantom-deps): debug is a direct runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:ansi-regex AI (phantom-deps): ansi-regex is a direct runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:strip-ansi AI (phantom-deps): strip-ansi is a direct runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:ansi-styles AI (phantom-deps): ansi-styles is a direct runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:pino-pretty AI (phantom-deps): pino-pretty is a direct runtime dependency; phantom-dep heuristic is a false positive. ai

Versions (showing 4 of 4)

Version Deps Published
2.83.0 18 / 55
2.82.0 18 / 56
2.78.0 21 / 54
2.77.0 21 / 54

v2.82.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: lfdt-npm → GitHub Actions (on 2026-03-27, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (lfdt-npm) on 2026-03-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v2.78.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.77.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.