Is Buildautomata Memory veilig?
Buildautomata Memory — Nerq Trust Score 45.6/100 (D-beoordeling). Score gebaseerd op 3 independent trust signals.
Buildautomata Memory is een software tool met een Nerq Vertrouwensscore van 45.6/100 (D), based on 3 onafhankelijke gegevensdimensies. Onderhoud: 0/100. Populariteit: 0/100. Gegevens afkomstig van meerdere openbare bronnen waaronder pakketregisters, GitHub, NVD, OSV.dev en OpenSSF Scorecard. Laatst bijgewerkt: n/a. Machineleesbare gegevens (JSON).
Is Buildautomata Memory veilig?
Vertrouwensscore details — Buildautomata Memory has a Nerq Trust Score of 45.6/100 (D). Measured across 3 independent trust signals.
Wat is de vertrouwensscore van Buildautomata Memory?
Buildautomata Memory heeft een Nerq Trust Score van 45.6/100 met het cijfer D. Deze score is gebaseerd op 3 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.
Wat zijn de belangrijkste beveiligingsbevindingen voor Buildautomata Memory?
Het sterkste signaal van Buildautomata Memory is onderhoud met 0/100. Er zijn geen bekende kwetsbaarheden gedetecteerd.
Wat is Buildautomata Memory en wie onderhoudt het?
| Ontwikkelaar | https://github.com/brucepro/buildautomata_memory_mcp |
| Categorie | Data |
| Sterren | 14 |
| Bron | https://github.com/brucepro/buildautomata_memory_mcp |
Populaire alternatieven in data
What Is Buildautomata Memory?
Buildautomata Memory is a software tool in the data category: BuildAutomata Memory offers persistent memory with advanced search and decay features for context onderhoud.. It has 14 GitHub stars. Nerq Trust Score: 46/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.
How Nerq Assesses Buildautomata Memory's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. Here is how Buildautomata Memory performs in each:
- Onderhoud (0/100): Buildautomata Memory is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentatie, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Gebaseerd op GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 45.6/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Buildautomata Memory?
Buildautomata Memory is commonly evaluated by:
- Developers and teams working with data tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Buildautomata Memory's measured signals (onderhoud 0/100, documentatie 0/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Buildautomata Memory's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Bekijk de repository beveiliging policy, open issues, and recent commits for signs of active onderhoud.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Buildautomata Memory's dependency tree. - Beoordeling permissions — Understand what access Buildautomata Memory requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Buildautomata Memory in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=BuildAutomata Memory - Bekijk de license — Confirm that Buildautomata Memory'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.
- 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 beveiliging concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Buildautomata Memory
When evaluating whether Buildautomata Memory is safe, consider these category-specific risks:
Understand how Buildautomata Memory processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Buildautomata Memory's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.
Regularly check for updates to Buildautomata Memory. Beveiliging patches and bug fixes are only effective if you're running the latest version.
If Buildautomata Memory 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.
Verify that Buildautomata Memory's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Buildautomata Memory in violation of its license can expose your organization to legal liability.
Best Practices for Using Buildautomata Memory Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Buildautomata Memory while minimizing risk:
Periodically review how Buildautomata Memory is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.
Ensure Buildautomata Memory and all its dependencies are running the latest stable versions to benefit from beveiliging patches.
Grant Buildautomata Memory only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Buildautomata Memory's beveiliging advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Buildautomata Memory is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Buildautomata Memory
Nerq's signals are one input. In the following situations, evaluate Buildautomata Memory's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Buildautomata Memory's measured trust score of 45.6/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Buildautomata Memory is suitable for any particular use.
How Buildautomata Memory 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. Buildautomata Memory's score of 45.6/100 is below the category average of 62/100.
This suggests that Buildautomata Memory trails behind many comparable data tools. Organizations with strict beveiliging 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 matig 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 Buildautomata Memory 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 onderhoud patterns change, Buildautomata Memory'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Buildautomata Memory's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=BuildAutomata Memory&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Buildautomata Memory are strengthening or weakening over time.
Buildautomata Memory vs Alternatieven
In the data category, Buildautomata Memory scores 45.6/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Buildautomata Memory vs firecrawl — Trust Score: 64.4/100
- Buildautomata Memory vs MinerU — Trust Score: 76.6/100
- Buildautomata Memory vs mindsdb — Trust Score: 68.1/100
Belangrijkste conclusies
- Buildautomata Memory has a measured Nerq Trust Score of 45.6/100 (D) — a composite of independent signals, not a suitability judgment.
- Among data tools, Buildautomata Memory scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — beveiliging, onderhoud, documentatie, naleving, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Veelgestelde vragen
Is Buildautomata Memory veilig?
Wat is de vertrouwensscore van Buildautomata Memory?
Wat zijn veiligere alternatieven voor Buildautomata Memory?
Hoe vaak wordt de beveiligingsscore van Buildautomata Memory bijgewerkt?
Kan ik Buildautomata Memory gebruiken in een gereguleerde omgeving?
Zie ook
Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.