Memory Markdown安全吗?

Memory Markdown — Nerq 信任评分 38.9/100 (E级). 基于5个信任维度的分析,被评估为存在重大安全风险。 最后更新:2026-04-02。

请对Memory Markdown保持警惕。 Memory Markdown is a software tool Nerq 信任评分为 38.9/100 (E). 低于推荐阈值 70。 Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-02. 机器可读数据(JSON).

Memory Markdown安全吗?

否——请谨慎使用 — Memory Markdown Nerq 信任评分为 38.9/100 (E). 信任信号低于平均水平,在安全性、维护或文档方面存在重大缺口. 未经彻底手动审查和额外安全措施,不建议用于生产环境.

安全分析 → {name}隐私报告 →

Memory Markdown的信任评分是多少?

Memory Markdown Nerq 信任评分为 38.9/100, earning a E grade. This score is based on 5 independently measured dimensions including security, maintenance, and community adoption.

整体信任度
38.9

Memory Markdown的主要安全发现是什么?

Memory Markdown's strongest signal is 整体信任度 at 38.9/100. No 已知漏洞 have been detected. It has not yet reached the Nerq Verified threshold of 70+.

综合信任评分: 38.9/100 基于所有可用信号

Memory Markdown是什么,谁在维护它?

开发者https://github.com/pavex/mcp-memory-md
类别uncategorized
来源https://github.com/pavex/mcp-memory-md

What Is Memory Markdown?

Memory Markdown is a software tool in the uncategorized category: Persistent memory for AI assistants stored in local Markdown files using pure PHP.. Nerq 信任评分: 39/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Memory Markdown's Safety

Nerq evaluates every software tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core dimensions: 安全性 (known CVEs, dependency vulnerabilities, security policies), 维护 (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).

Memory Markdown receives an overall 信任评分 of 38.9/100 (E), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=Memory Markdown

Each dimension is weighted according to its importance for the tool's category. For example, Security and Maintenance carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Memory Markdown's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensions, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Should Use Memory Markdown?

Memory Markdown is designed for:

Risk guidance: We recommend caution with Memory Markdown. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Memory Markdown's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for 已知漏洞 in Memory Markdown's dependency tree.
  3. 评论 permissions — Understand what access Memory Markdown requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Memory Markdown in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=Memory Markdown
  6. 查看 license — Confirm that Memory Markdown's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
  7. Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Memory Markdown

When evaluating whether Memory Markdown is safe, consider these category-specific risks:

Data handling

Understand how Memory Markdown processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Memory Markdown's dependency tree for 已知漏洞. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Memory Markdown. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Memory Markdown connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.

License and IP compliance

Verify that Memory Markdown's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Memory Markdown in violation of its license can expose your organization to legal liability.

Best Practices for Using Memory Markdown Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Memory Markdown while minimizing risk:

Conduct regular audits

Periodically review how Memory Markdown is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Memory Markdown and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Memory Markdown only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Memory Markdown's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Memory Markdown is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Memory Markdown?

Even promising tools aren't right for every situation. Consider avoiding Memory Markdown in these scenarios:

For each scenario, evaluate whether Memory Markdown的信任评分为 38.9/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Memory Markdown Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average 信任评分 is 62/100. Memory Markdown's score of 38.9/100 is below the category average of 62/100.

This suggests that Memory Markdown trails behind many comparable uncategorized tools. Organizations with strict security requirements should evaluate whether higher-scoring alternatives better meet their needs.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

信任评分 History

Nerq continuously monitors Memory Markdown and recalculates its 信任评分 as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Memory Markdown's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Memory Markdown's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Memory Markdown&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Memory Markdown are strengthening or weakening over time.

主要结论

常见问题

Memory Markdown可以安全使用吗?
请保持警惕。 Memory Markdown Nerq 信任评分为 38.9/100 (E). 最强信号: 整体信任度 (38.9/100). 评分基于 多个信任维度.
Memory Markdown's trust score是什么?
Memory Markdown: 38.9/100 (E). 评分基于: 多个信任维度. 评分会在新数据可用时更新。 API: GET nerq.ai/v1/preflight?target=Memory Markdown
Memory Markdown有哪些更安全的替代品?
In the uncategorized category, more software tools are being analyzed — 请稍后再查看. Memory Markdown scores 38.9/100.
How often is Memory Markdown's safety score updated?
Nerq continuously monitors Memory Markdown and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 38.9/100 (E), last verified 2026-04-02. API: GET nerq.ai/v1/preflight?target=Memory Markdown
我可以在受监管环境中使用Memory Markdown吗?
Memory Markdown has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq 信任评分是基于公开信号的自动评估。它们不构成建议或保证。请始终进行自己的验证。

We use cookies for analytics and caching. 隐私 Policy