Czy Anamnese jest bezpieczny?

Anamnese — Nerq Trust Score 38.9/100 (Ocena E). Wynik oparty na 5 independent trust signals.

Anamnese to software tool z wynikiem zaufania Nerq 38.9/100 (E). Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: n/a. Dane odczytywalne maszynowo (JSON).

Czy Anamnese jest bezpieczny?

Szczegóły wyniku zaufania — Anamnese has a Nerq Trust Score of 38.9/100 (E). Measured across 1 independent trust signal.

Analiza bezpieczeństwa → Raport prywatności Anamnese →

Jaki jest wynik zaufania Anamnese?

Anamnese ma Nerq Trust Score 38.9/100 z oceną E. Ten wynik opiera się na 5 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.

Ogólne zaufanie
38.9

Jakie są kluczowe ustalenia bezpieczeństwa dla Anamnese?

Najsilniejszy sygnał Anamnese to ogólne zaufanie na poziomie 38.9/100. Nie wykryto znanych luk w zabezpieczeniach.

⚠Łączny wynik zaufania: 38.9/100 ze wszystkich dostępnych sygnałów

Czym jest Anamnese i kto go utrzymuje?

Autorhttps://github.com/anamneseai/anamnese-plugin-marketplace
KategoriaUncategorized
Źródłohttps://github.com/anamneseai/anamnese-plugin-marketplace

What Is Anamnese?

Anamnese is a software tool in the uncategorized category: Personal memory and productivity layer for AI assistants with cloud-synced facts, tasks, goals, and notes.. Nerq Trust Score: 39/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.

How Nerq Assesses Anamnese'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 wymiarów: Bezpieczeństwo (known CVEs, dependency vulnerabilities, bezpieczeństwo policies), Konserwacja (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).

Anamnese receives an overall Trust Score of 38.9/100 (E). This is a measured composite, not a suitability judgment.

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

Each dimension is weighted according to its importance for the tool's category. For example, Bezpieczeństwo and Konserwacja 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 Anamnese's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five wymiarów, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Typically Evaluates Anamnese?

Anamnese is commonly evaluated by:

How to read the signals: Anamnese's measured signals (the trust signals above) 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 Anamnese's Safety Yourself

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

  1. Check the source code — Sprawdź repository bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Anamnese's dependency tree.
  3. Opinia permissions — Understand what access Anamnese requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Anamnese 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=Anamnese
  6. Sprawdź license — Confirm that Anamnese'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 bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Anamnese

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

Data handling

Understand how Anamnese processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency bezpieczeństwo

Check Anamnese's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.

Update frequency

Regularly check for updates to Anamnese. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Anamnese 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 zgodność

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

Best Practices for Using Anamnese Safely

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

Conduct regular audits

Periodically review how Anamnese is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.

Keep dependencies updated

Ensure Anamnese and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.

Follow least privilege

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

Monitor for bezpieczeństwo advisories

Subscribe to Anamnese's bezpieczeństwo 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 Anamnese is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Anamnese

Nerq's signals are one input. In the following situations, evaluate Anamnese's measured signals against your own requirements before making a decision:

For each situation, compare Anamnese's measured trust score of 38.9/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Anamnese is suitable for any particular use.

How Anamnese Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Anamnese's score of 38.9/100 is below the category average of 62/100.

This suggests that Anamnese trails behind many comparable uncategorized tools. Organizations with strict bezpieczeństwo 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 umiarkowany 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 Anamnese 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 konserwacja patterns change, Anamnese'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 bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Anamnese's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Anamnese&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 — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Anamnese are strengthening or weakening over time.

Kluczowe wnioski

Często zadawane pytania

Czy Anamnese jest bezpieczny?
Anamnese z wynikiem zaufania Nerq 38.9/100 (E). Najsilniejszy sygnał: ogólne zaufanie (38.9/100). Wynik oparty na multiple trust wymiarów.
Jaki jest wynik zaufania Anamnese?
Anamnese: 38.9/100 (E). Wynik oparty na multiple trust wymiarów. Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=Anamnese
Jakie są bezpieczniejsze alternatywy dla Anamnese?
W kategorii Uncategorized, więcej software tool jest analizowanych — sprawdź wkrótce. Anamnese scores 38.9/100.
Jak często aktualizowana jest ocena bezpieczeństwa Anamnese?
Nerq recomputes Anamnese's trust score as new data becomes available. Current: 38.9/100 (E). API: GET nerq.ai/v1/preflight?target=Anamnese
Czy mogę używać Anamnese w środowisku regulowanym?
Anamnese: 38.9/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Zobacz także

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

Używamy plików cookie do analiz i buforowania. Prywatność