future-architect/vuls · Security & risks

Authoritative risk signals for future-architect/vuls — dependency CVEs (deps.dev), OpenSSF Scorecard, and GitHub Code Scanning. Not a substitute for your own security review.

Architecture Security & risks Dependencies License Maintenance Alternatives Vs Full analysis

Dependency CVEs (deps.dev)

Critical

0 direct

High

0 direct

Moderate

Deps scanned

25 direct

GO-2026-4919 · github.com/aquasecurity/trivy (direct)Trivy ecosystem supply chain was briefly compromised in github.com/aquasecurity/trivyMODERATE

OpenSSF Scorecard · 8.6/10

Fuzzing0/10
CII-Best-Practices2/10
Branch-Protection5/10
Vulnerabilities7/10
Signed-Releases8/10
Security-Policy9/10
Dangerous-Workflow10/10
Dependency-Update-Tool10/10

GitHub Code Scanning · 0 open / 0 total

Tools: —

Ask AI about future-architect/vuls

Grounded in the actual source code. Pick a starter question or write your own.

What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.