contextbase-coding-agents
ContextBase long-term memory for coding agents; remote connection required.
This report shows the evidence for contextbase-coding-agents@1.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package silently launches a paid-capable local agent for first-time repository seeding by default, using the user’s existing CLI authentication without an explicit survey request. The $2 Claude budget cap limits the charge but does not provide consent for the automatic spend.
Decision evidence
public snapshot- Hook configuration defaults autoSeed and codebaseSurvey to enabled, selects haiku, and sets surveyBudgetUsd to 2.
- When a project has no existing git records, the seeding path calls the survey runner automatically.
- The Claude survey command runs non-interactively with --max-budget-usd defaulting to 2; its allowed tools include reading and ContextBase ingestion.
- A supervisor launches the selected CLI with output ignored, while the supervisor itself is detached.
- The package is intended to connect to a user-provided memory service, and its bearer token is sent to the configured API URL.
- The survey is a one-time repository-seeding feature aligned with the package’s stated coding-agent memory purpose.
- The Claude survey restricts tools and sets a spending cap, and the memory API endpoint is configured by the user.
Source & flagged code
8 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/zcode-hook.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to contextbase-coding-agents@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing contextbase-coding-agents@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.