jazzband/web3-devkit-cli

scanned 2026-06-30 · git a5994b9

3 of 6 checks flagged a security issue

🟡 Worth a look

Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets1Vulnerable dependencies3Known OSS vulnerabilities4Risky code patterns✓Malicious dependencies—Project health10

Security checks

Leaked secrets — Gitleaksⓘ 1 found

API keys, passwords or tokens committed into the repo.

Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

.env:1

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 3 found

Packages you depend on that have known security holes (CVEs).

Worth fixing CVE-2026-41907 uuid: uuid: Out-of-bounds write vulnerability impacts data integrity and confidentiality

package-lock.json

A package you depend on has a known security hole (CVE-2026-41907). Fix: Update that package to its patched version.
Worth fixing CVE-2026-48779 ws: ws: Denial of Service via memory exhaustion from small WebSocket fragments

package-lock.json

A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.
Worth fixing CVE-2026-48779 ws: ws: Denial of Service via memory exhaustion from small WebSocket fragments

package-lock.json

A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 4 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-3gc7-fjrx-p6mg bigint-buffer Vulnerable to Buffer Overflow via toBigIntLE() Function

/workdirs/scan-511b0aff-b319-4ce4-a764-39d2898aca88/package-lock.json

A package you depend on has a known security hole (CVE-2025-3194). Fix: Update that package to its patched version.
Worth fixing GHSA-w5hq-g745-h8pq uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

/workdirs/scan-511b0aff-b319-4ce4-a764-39d2898aca88/package-lock.json

A package you depend on has a known security hole (CVE-2026-41907). Fix: Update that package to its patched version.
Worth fixing GHSA-96hv-2xvq-fx4p ws: Memory exhaustion DoS from tiny fragments and data chunks

/workdirs/scan-511b0aff-b319-4ce4-a764-39d2898aca88/package-lock.json

A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.
Worth fixing GHSA-96hv-2xvq-fx4p ws: Memory exhaustion DoS from tiny fragments and data chunks

/workdirs/scan-511b0aff-b319-4ce4-a764-39d2898aca88/package-lock.json

A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited — injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ couldn’t run

Packages that look intentionally malicious — typosquats, sneaky install scripts.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: npm:Traceback (most recent call last): File "/usr/local/bin/guarddog", line 5, in <module> from guarddog.cli import cl

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ 10 notes

Maintenance & supply-chain hygiene. A signal about the project — not a vulnerability in your code.

Worth fixing scorecard-overall OpenSSF Scorecard overall: 1.4/10

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Code-Review Code-Review scored 0: Found 0/3 approved changesets -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Contributors Contributors scored 0: project has 0 contributing companies or organizations -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detected

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-License License scored 0: license file not detected

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Maintained Maintained scored 0: project was created within the last 90 days. Please review its contents carefully

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-SAST SAST scored 0: no SAST tool detected

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.

via OpenSSF Scorecard v5.5.0 · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.