Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for practitioners who want agent workflows to call real APIs without handing the agent long-lived plaintext credentials in environment variables or prompt context.
Who should use it
Who should skip it
Pass on inflightsec/agent-vault-proxy if its scope or audience does not match what your team is building right now.
About this signal
inflightsec/agent-vault-proxy is tracked by RepoRadar as a secret proxy in the Security section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for inflightsec/agent-vault-proxy are workflow potential (9.1) and open-source/build quality (8.4), while momentum (5.0) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned inflightsec/agent-vault-proxy a composite score of 8.0 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
AVP terminates and rewrites outbound requests on the local proxy path, so validate the TLS trust and secret-substitution flow before routing high-value production keys through it; The Bitwarden-backed path adds another secrets dependency and the static mode stores secrets locally for later injection, so keep the first pilot on low-privilege keys.