xai-org/grok-1

scanned 2026-05-27 · git 7050ed2

2 of 6 checks flagged a security issue

🟡 Worth a look

6 checks ran. Start with vulnerable dependencies below.

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

Leaked secrets✓Vulnerable dependencies1Known OSS vulnerabilities1Risky code patterns✓Malicious dependencies✓Project health9

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 1 found

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

Worth fixing CVE-2026-1260 sentencepiece: Sentencepiece: Invalid memory access leading to potential arbitrary code execution via a crafted model file.

requirements.txt

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

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 1 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-38vq-g6vr-w8wf Sentencepiece has a a heap overflow issue

/workdirs/scan-e7575804-8b2e-404e-8135-d66528f60e8a/requirements.txt

A package you depend on has a known security hole. 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ⓘ none found ✓

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

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

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ⓘ 9 notes

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

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

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-CI-Tests CI-Tests scored 0: 0 out of 4 merged PRs checked by a CI test -- score normalized to 0

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-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-Maintained Maintained scored 0: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
Minor scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0

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.