mem-fs-editor
npmIs mem-fs-editor safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for mem-fs-editor v11.1.4. Trust score: 75/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
mem-fs-editor Passed Security Checks
No security concerns detected
0
0
0
No Concerns Detected
No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
mem-fs-editor Capabilities & Permissions
What mem-fs-editor can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Filesystem Access
Reads and writes to the filesystem.
AGENTS.md for mem-fs-editor
Good instructions lead to good results. brin adds mem-fs-editor documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
mem-fs-editor Documentation & Source Code
For the full mem-fs-editor README, API documentation, and source code, visit the official package registry.
Frequently asked questions about mem-fs-editor safety
Install (safety-checked)
Weekly Downloads
Version
11.1.4License
MITLast Scanned
Trust Score
Capabilities
Reads & Writes files