← Home

@layerzerolabs/vm-tooling

npm
45
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

layerzero-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/5DYPW3MY.js AI (source-diff): Bundled tsup output (js-tokens/zx deps), not a loader; no malicious behavior in sample. ai
source-diff net-exec-file:dist/5XQTITZP.js AI (source-diff): Bundled tsup output containing tokenizer/zx deps, not a dropper; verified via sample. ai
source-diff net-exec-file:dist/IIZVEHVD.js AI (source-diff): Bundled build output (tsup/esbuild chunk), not a dropper; matches known publisher's bundling pattern. ai
source-diff net-exec-file:dist/DVALPAAO.js AI (source-diff): Bundled tsup build output (imports bundler chunk, js-tokens), not a dropper/loader. ai
source-diff net-exec-file:dist/5PWUQUE5.js AI (source-diff): Bundled tsup build output, not a dropper; pattern recurs across this monorepo's packages. ai
publish-pattern new-deps-added AI (publish-pattern): glob/yaml/p-limit are common, well-known utility deps fitting a tooling package. ai
source-diff net-exec-file:dist/5GPTK3MH.js AI (source-diff): Bundled tsup output containing standard tokenizer/network libs, not an injected dropper. ai
source-diff large-new-source-files AI (source-diff): Expected growth from bundler output across skipped versions, not injected code. ai
npm-metadata no-description AI (npm-metadata): Internal monorepo tooling; missing description is cosmetic and stable across versions. ai
bogus-package bogus-package AI (bogus-package): Internal tooling package from established layerzero-bot publisher; sparse metadata is expected for monorepo tooling. ai
semgrep semgrep:dynamic-require AI (semgrep): CLI launcher pattern: requires a known local built path, not user-controlled input. ai

Versions (showing 45 of 145)

Version Deps Published
0.2.25 6 / 11
0.2.24 6 / 11
0.2.23 6 / 11
0.2.22 5 / 12
0.2.21 5 / 12
0.2.20 5 / 12
0.2.19 5 / 12
0.2.18 5 / 12
0.2.15 5 / 12
0.2.13 5 / 12
0.2.12 5 / 12
0.2.11 5 / 12
0.2.10 5 / 12
0.2.9 5 / 12
0.2.8 6 / 12
0.2.7 7 / 12
0.2.6 7 / 12
0.2.5 7 / 12
0.0.75 7 / 12
0.0.74 7 / 12
0.0.73 7 / 12
0.0.67 8 / 12
0.0.66 8 / 12
0.0.65 8 / 12
0.0.64 8 / 12
0.0.63 8 / 12
0.0.62 8 / 12
0.0.61 8 / 12
0.0.60 7 / 12
0.0.59 7 / 12
0.0.48 5 / 11
0.0.47 5 / 11
0.0.46 5 / 11
0.0.45 5 / 11
0.0.44 5 / 11
0.0.43 5 / 11
0.0.42 5 / 11
0.0.41 5 / 11
0.0.40 5 / 11
0.0.35 5 / 11
0.0.34 5 / 11
0.0.33 5 / 11
0.0.32 5 / 11
0.0.31 5 / 11
0.0.30 5 / 11

v0.2.22

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.21

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.20

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.19

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.18

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.15

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.13

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.2.11

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.10

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.9

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.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.

v0.2.7

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.6

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.5

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.75

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.74

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.73

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.67

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.66

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.65

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.64

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.63

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.62

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.61

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.60

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.59

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.