← Home

@layerzerolabs/chain-utils

npm
12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

layerzero-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@layerzerolabs/common-ton AI (dependencies): First-party LayerZero monorepo package at matching version 0.2.32. ai
dependencies unvetted-dep:@initia/initia.js AI (dependencies): Pinned at 1.0.4 in a well-established LayerZero package; consistent across versions with no other risk signals. ai
provenance no-provenance AI (provenance): Publisher has 770 approved packages without provenance; consistent ecosystem pattern. ai
bogus-package bogus-package AI (bogus-package): Monorepo utility package; missing metadata is a consistent pattern across the layerzerolabs ecosystem, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent with layerzerolabs monorepo publishing pattern; not indicative of malice. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.100 9 / 5
0.2.96 9 / 5
0.2.90 9 / 5
0.2.87 9 / 5
0.2.84 9 / 5
0.2.82 9 / 5
0.2.50 9 / 5
0.2.46 9 / 5
0.2.32 9 / 5
0.2.28 9 / 5
0.2.12 9 / 5
0.0.8 5 / 4

v0.2.100

1 finding
LOW No provenance attestation provenance

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

v0.2.96

1 finding
LOW No provenance attestation provenance

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

v0.2.90

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.

v0.2.87

1 finding
LOW No provenance attestation provenance

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

v0.2.84

1 finding
LOW No provenance attestation provenance

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

v0.2.50

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.

v0.2.46

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.

v0.2.32

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.

v0.2.28

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.

v0.2.12

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.

v0.0.8

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.