Is Opencode Named Memory Safe?

Opencode Named Memory — Nerq Trust Score 60.5/100 (C+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-07-23.

Use Opencode Named Memory with some caution. Opencode Named Memory is a npm package with a Nerq Trust Score of 60.5/100 (C+), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).

Safety Guide: Opencode Named Memory

What is Opencode Named Memory?

Opencode Named Memory is a Node.js package — Named persistent memory plugin for OpenCode - gives each agent or project its own long-term memory store backed by a local SQLite database.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=opencode-named-memory

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Opencode Named Memory has a Nerq Trust Score of 60/100 (C+) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

• Opencode Named Memory has a Trust Score of 60/100 (C+).
• Review carefully before use — below trust threshold.
• Always verify independently using the Nerq API.

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.