hydrascope@0.1.1
VERIFIED· not startedPublisher claims: "Structural graph context, temporal SUPERSEDES lineage, and 4-axis ontology MCP on HydraDB." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
INTERNAL_HOST_TOKENConfiguration, not credentials: EMBED_MODEL, HYDRASCOPE_BRICK_DB_PATH, HYDRASCOPE_WORKSPACE_ROOT, MOCK_EMBEDDINGS, OLLAMA_EMBED_HOST, QUEUE_MAX_STALL_MS, REDIS_FAILOVER_JITTER_MS- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for INTERNAL_HOST_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 18 s · 2 scenarios · 0 deviationsStatic findings
".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN mkdir -p /app/data /app/logs && chown -R node:node /appFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod 0644 /data/auth-tokenFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.const ENV_TEMPLATE_NAMES = new Set(['.env.example', '.env.sample', '.env.template']);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.COPY config.json .env.example LICENSE README.md ./Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod -R 0777 /data/store /data/node-data-cacheFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.const bracketEnvRe = /\bprocess\.env\[\s*['"]([A-Z][A-Z0-9_]{1,80})['"]\s*\]/g;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const dotEnvRe = /\bprocess\.env\.([A-Z][A-Z0-9_]{1,80})\b/g;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for hydrascope@0.1.1 as of 44 min ago. This is the package itself, not its dependencies.