Is Key Value Extractor Safe?

Key Value Extractor — Nerq Trust Score 42.5/100 (E grade). Based on analysis of 3 trust dimensions, it is has notable safety concerns. Last updated: 2026-05-13.

Exercise caution with Key Value Extractor. Key Value Extractor is a software tool with a Nerq Trust Score of 42.5/100 (E), based on 3 independent data dimensions. Below the recommended threshold of 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-05-13. Machine-readable data (JSON).

Is Key Value Extractor safe?

NO — USE WITH CAUTION — Key Value Extractor has a Nerq Trust Score of 42.5/100 (E). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Security Analysis → Key Value Extractor Privacy Report →

What is Key Value Extractor's trust score?

Key Value Extractor has a Nerq Trust Score of 42.5/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.

Maintenance
0
Documentation
0
Popularity
0

What are the key security findings for Key Value Extractor?

Key Value Extractor's strongest signal is maintenance at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 1 stars on pulsemcp

What is Key Value Extractor and who maintains it?

Authorhttps://github.com/kunihiros/kv-extractor-mcp-server
CategoryData
Stars1
Sourcehttps://github.com/kunihiros/kv-extractor-mcp-server

Popular Alternatives in data

firecrawl/firecrawl
58.8/100 · C
github
MinerU
63.7/100 · C+
github
mindsdb/mindsdb
49.3/100 · D+
github
PostHog
51.9/100 · D
pulsemcp
Graphiti
61.5/100 · C+
pulsemcp

What Is Key Value Extractor?

Key Value Extractor is a software tool in the data category: Extracts structured key-value pairs from unstructured text.. It has 1 GitHub stars. Nerq Trust Score: 42/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 Key Value Extractor's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Key Value Extractor performs in each:

The overall Trust Score of 42.5/100 (E) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Key Value Extractor?

Key Value Extractor is designed for:

Risk guidance: We recommend caution with Key Value Extractor. 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 Key Value Extractor'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 known vulnerabilities in Key Value Extractor's dependency tree.
  3. Review permissions — Understand what access Key Value Extractor requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Key Value Extractor 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=Key-Value Extractor
  6. Review the license — Confirm that Key Value Extractor'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 Key Value Extractor

When evaluating whether Key Value Extractor is safe, consider these category-specific risks:

Data handling

Understand how Key Value Extractor 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 Key Value Extractor's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

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

Third-party integrations

If Key Value Extractor 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 Key Value Extractor's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Key Value Extractor in violation of its license can expose your organization to legal liability.

Best Practices for Using Key Value Extractor Safely

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

Conduct regular audits

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

Keep dependencies updated

Ensure Key Value Extractor and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Key Value Extractor only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Key Value Extractor'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 Key Value Extractor is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Key Value Extractor?

Even promising tools aren't right for every situation. Consider avoiding Key Value Extractor in these scenarios:

For each scenario, evaluate whether Key Value Extractor's trust score of 42.5/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Key Value Extractor Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among data tools, the average Trust Score is 62/100. Key Value Extractor's score of 42.5/100 is below the category average of 62/100.

This suggests that Key Value Extractor trails behind many comparable data 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.

Trust Score History

Nerq continuously monitors Key Value Extractor and recalculates its Trust Score 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, Key Value Extractor'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 Key Value Extractor's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Key-Value Extractor&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 Key Value Extractor are strengthening or weakening over time.

Key Value Extractor vs Alternatives

In the data category, Key Value Extractor scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Key Takeaways

Detailed Score Analysis

DimensionScore
Maintenance0/100
Popularity0/100

Based on 2 dimensions. Data from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Key Value Extractor collect?

Privacy assessment for Key Value Extractor is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Is Key Value Extractor secure?

Security score: under assessment. Review security practices and consider alternatives with higher security scores for sensitive use cases.

Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.

Full analysis: Key Value Extractor Security Report

How we calculated this score

Key Value Extractor's trust score of 42.5/100 (E) is computed from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 2 independent dimensions: maintenance (0/100), popularity (0/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on May 13, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Key Value Extractor Safe?
Exercise caution. Key-Value Extractor with a Nerq Trust Score of 42.5/100 (E). Strongest signal: maintenance (0/100). Score based on Maintenance (0/100), Popularity (0/100), Documentation (0/100).
What is Key Value Extractor's trust score?
Key-Value Extractor: 42.5/100 (E). Score based on Maintenance (0/100), Popularity (0/100), Documentation (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=Key-Value Extractor
What are safer alternatives to Key Value Extractor?
In the Data category, higher-rated alternatives include firecrawl/firecrawl (59/100), MinerU (64/100), mindsdb/mindsdb (49/100). Key-Value Extractor scores 42.5/100.
How often is Key Value Extractor's safety score updated?
Nerq continuously monitors Key Value Extractor and updates its trust score as new data becomes available. Current: 42.5/100 (E), last verified 2026-05-13. API: GET nerq.ai/v1/preflight?target=Key-Value Extractor
Can I use Key Value Extractor in a regulated environment?
Key Value Extractor has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended.
API: /v1/preflight Trust Badge API Docs

See Also

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

We use cookies for analytics and caching. Privacy