Skip to main content
hc
Submit
statuslinesSource-backed

OSV Dependency Risk Statusline

Claude Code statusline that reads OSV-Scanner JSON results and prints a compact dependency vulnerability count for review sessions.

by MkDev11·added 2026-06-04·
Claude Code
HarnessClaude Code
Language:bash
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/statuslines/osv-dependency-risk-statusline
Source URLs
https://google.github.io/osv-scanner/, https://github.com/google/osv-scanner
Safety notes
Prefer reading a precomputed report; scanning dependencies during every statusline refresh can be slow., Auto-scan mode refuses symlinked report paths and writes through a temporary file before replacing the report., Vulnerability counts need human triage for reachability, exploitability, and acceptable remediation timing., Do not let a zero count replace lockfile review, provenance checks, or package-manager audit policy.
Privacy notes
OSV reports can reveal package names, versions, ecosystems, and repository structure., The statusline prints only the count, but the local JSON report may contain detailed dependency metadata., If scans run against private package manifests, review where the scanner sends package coordinates.
Author
MkDev11
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Config edit

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

1 listed

Install type

Config edit

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime1Network & hosting2

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 3 risk areas.

3 areas
  • SafetyGeneralPrefer reading a precomputed report; scanning dependencies during every statusline refresh can be slow.
  • SafetyLocal filesAuto-scan mode refuses symlinked report paths and writes through a temporary file before replacing the report.
  • SafetyGeneralVulnerability counts need human triage for reachability, exploitability, and acceptable remediation timing.
  • SafetyLocal filesDo not let a zero count replace lockfile review, provenance checks, or package-manager audit policy.
  • PrivacyGeneralOSV reports can reveal package names, versions, ecosystems, and repository structure.
  • PrivacyGeneralThe statusline prints only the count, but the local JSON report may contain detailed dependency metadata.
  • PrivacyExecution & processesIf scans run against private package manifests, review where the scanner sends package coordinates.

Safety notes

  • Prefer reading a precomputed report; scanning dependencies during every statusline refresh can be slow.
  • Auto-scan mode refuses symlinked report paths and writes through a temporary file before replacing the report.
  • Vulnerability counts need human triage for reachability, exploitability, and acceptable remediation timing.
  • Do not let a zero count replace lockfile review, provenance checks, or package-manager audit policy.

Privacy notes

  • OSV reports can reveal package names, versions, ecosystems, and repository structure.
  • The statusline prints only the count, but the local JSON report may contain detailed dependency metadata.
  • If scans run against private package manifests, review where the scanner sends package coordinates.

Prerequisites

  • OSV-Scanner JSON report at `osv-report.json`, or OSV_STATUSLINE_JSON set to another report path.
  • jq available for reading the report.
  • Optional OSV-Scanner CLI installed if OSV_STATUSLINE_SCAN is set to 1.

Schema details

Install type
config
Troubleshooting
No
Source repository stats
Scope
Source repo
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash
set -u

main() {
report="${OSV_STATUSLINE_JSON:-osv-report.json}"

if [ "${OSV_STATUSLINE_SCAN:-0}" = "1" ] && command -v osv-scanner >/dev/null 2>&1; then
  if [ -L "$report" ]; then
    echo "deps: unsafe report path"
    exit 0
  fi

  report_dir=$(dirname "$report")
  tmp_report=$(mktemp "$report_dir/.osv-report.XXXXXX") || exit 0
  trap 'rm -f "$tmp_report"' EXIT

  osv-scanner --format json . > "$tmp_report" 2>/dev/null || true
  if [ -s "$tmp_report" ] && { ! command -v jq >/dev/null 2>&1 || jq -e . "$tmp_report" >/dev/null 2>&1; }; then
    mv -f "$tmp_report" "$report"
    trap - EXIT
  fi
fi

if [ ! -f "$report" ]; then
  echo "deps: osv report missing"
  exit 0
fi
if ! command -v jq >/dev/null 2>&1; then
  echo "deps: jq missing"
  exit 0
fi

count=$(jq '[.. | objects | .vulnerabilities? // empty | .[]] | length' "$report" 2>/dev/null || echo 0)
if [ "$count" -gt 0 ]; then
  state="review"
else
  state="ok"
fi

printf 'deps: vulns %s | %s\n' "$count" "$state"
}

case $- in
  *n*) ;;
  *) main "$@" ;;
esac
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/osv-dependency-risk-statusline.sh"
  }
}

About this resource

Source notes

  • OSV-Scanner documentation describes scanning dependency manifests and emitting JSON output for automation.
  • This statusline reads a report by default so teams can run scans on their own cadence and keep Claude Code refreshes fast.

Duplicate check

Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for osv-dependency-risk-statusline, OSV-Scanner, dependency risk, vulnerability count, and dependency statuslines. No statusline entry or open PR with this slug or OSV source was found.

Disclosure

Editorial statusline recipe. No paid placement or affiliate link is used.

#dependencies#security#osv#claude-code

Source citations

Add this badge to your README

Show that OSV Dependency Risk Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/osv-dependency-risk-statusline.svg)](https://heyclau.de/entry/statuslines/osv-dependency-risk-statusline)

How it compares

OSV Dependency Risk Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field
OSV Dependency Risk Statusline

Claude Code statusline that reads OSV-Scanner JSON results and prints a compact dependency vulnerability count for review sessions.

Open dossier
git-secrets Environment Risk Statusline

Claude Code statusline that surfaces sensitive environment-file risk and can optionally run git-secrets as a local pre-commit-style scanner.

Open dossier
GitHub logoGitHub Search Review Queue Statusline

Claude Code statusline that uses GitHub pull request search qualifiers to show review-requested queue counts for maintainers.

Open dossier
MCP Auth Surface Statusline

Claude Code statusline that summarizes MCP server count, remote endpoint count, and credential-surface hints without printing tokens, secrets, local paths, or full endpoint URLs.

Open dossier
Next stepsDiffers
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersMkDev11MkDev11MkDev11JSONbored
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand——GitHub logoGitHub—
Categorystatuslinesstatuslinesstatuslinesstatuslines
SourceSource-backedSource-backedSource-backedSource-backed
AuthorMkDev11MkDev11MkDev11JSONbored
Added2026-06-042026-06-042026-06-042026-06-05
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Harness
Claude Code
Claude Code
Claude Code
Claude Code
Source repo————
Safety notes✓Prefer reading a precomputed report; scanning dependencies during every statusline refresh can be slow. Auto-scan mode refuses symlinked report paths and writes through a temporary file before replacing the report. Vulnerability counts need human triage for reachability, exploitability, and acceptable remediation timing. Do not let a zero count replace lockfile review, provenance checks, or package-manager audit policy.✓The default mode does not scan file contents; it only counts sensitive-looking environment files in Git status. Enable recursive git-secrets scanning only in repositories where you are authorized to inspect all files. Scanner mode invokes the git-secrets executable directly and does not fall back to Git aliases. Treat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR.✓Queue counts help with triage but do not rank urgency, security impact, or release blockers. Draft PRs are excluded from the ready count, but repositories may use labels or checks for additional readiness rules. Keep the refresh interval moderate to avoid repeated GitHub search calls.✓This statusline is advisory and should not be used as the only MCP authorization review. It intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values. Remote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
Privacy notes✓OSV reports can reveal package names, versions, ecosystems, and repository structure. The statusline prints only the count, but the local JSON report may contain detailed dependency metadata. If scans run against private package manifests, review where the scanner sends package coordinates.✓The default output prints counts only and does not print filenames or matched values. Recursive scans read repository files and may inspect sensitive local material. Terminal recordings can still reveal that a workspace contains sensitive environment files.✓The script prints aggregate counts only, not PR titles, authors, or branch names. Private review requests follow the local GitHub account and may reveal workload size in screenshots. Organization review-team rules may cause counts to differ from the GitHub web UI.✓The statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint. Avoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
Prerequisites
  • OSV-Scanner JSON report at `osv-report.json`, or OSV_STATUSLINE_JSON set to another report path.
  • jq available for reading the report.
  • Optional OSV-Scanner CLI installed if OSV_STATUSLINE_SCAN is set to 1.
  • Git installed and the command run from a repository worktree.
  • Optional git-secrets installed if GIT_SECRETS_STATUSLINE_SCAN is set to 1.
  • A slower refresh interval when optional scanning is enabled, because recursive scans can be expensive.
  • GitHub CLI installed and logged in as the maintainer account whose review queue should be shown.
  • jq available for counting pull request fields.
  • Repository access that lets GitHub search return pull requests requesting the current account's review.
  • Claude Code CLI with statusline support.
  • jq installed locally.
  • MCP server metadata available in the Claude Code statusline input.
Install———
mkdir -p .claude/statuslines
tmp="$(mktemp .claude/statuslines/mcp-auth-surface.sh.XXXXXX)"
cat > "$tmp" <<'EOF'
#!/usr/bin/env bash
set -u

input=$(cat)
if ! command -v jq >/dev/null 2>&1; then
  printf 'MCP auth: jq unavailable\n'
  exit 0
fi

servers=$(printf '%s' "$input" | jq -c '.mcp.servers // []' 2>/dev/null || printf '[]')
server_count=$(printf '%s' "$servers" | jq 'length' 2>/dev/null || printf '0')
remote_count=$(printf '%s' "$servers" | jq '[.[] | select((.url // .endpoint // "") | test("^https?://"))] | length' 2>/dev/null || printf '0')
credential_hint=$(printf '%s' "$servers" | jq '[.[] | select((.auth // .authorization // .headers // .env // null) != null)] | length' 2>/dev/null || printf '0')

if [ "$credential_hint" -gt 0 ]; then
  state="credentials: review"
else
  state="credentials: none shown"
fi

printf 'MCP auth: %s servers | %s remote | %s\n' "$server_count" "$remote_count" "$state"
EOF
chmod 700 "$tmp"
mv -f "$tmp" .claude/statuslines/mcp-auth-surface.sh
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/osv-dependency-risk-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-secrets-env-risk-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/github-search-review-queue-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-auth-surface.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Claude Code Subagents For Repository Maintenance

Use focused subagents for recurring repository maintenance tasks.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.