Czy Tams jest bezpieczny?

Tams — Nerq Trust Score 62.2/100 (Ocena C). Wynik oparty na 4 independent trust signals.

Tams to software tool z wynikiem zaufania Nerq 62.2/100 (C), based on 4 niezależnych wymiarów danych. Bezpieczeństwo: 0/100. Konserwacja: 1/100. Popularność: 0/100. 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 Tams jest bezpieczny?

Szczegóły wyniku zaufania — Tams has a Nerq Trust Score of 62.2/100 (C). Measured across 4 independent trust signals.

Analiza bezpieczeństwa → Raport prywatności Tams →

Jaki jest wynik zaufania Tams?

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

Bezpieczeństwo
0
Konserwacja
1
Dokumentacja
1
Popularność
0

Jakie są kluczowe ustalenia bezpieczeństwa dla Tams?

Najsilniejszy sygnał Tams to konserwacja na poziomie 1/100. Nie wykryto znanych luk w zabezpieczeniach.

Ocena bezpieczeństwa: 0/100 (słaby)
Konserwacja: 1/100 — niska aktywność konserwacji
Dokumentacja: 1/100 — ograniczona dokumentacja
Popularność: 0/100 — 6 gwiazdek na github

Czym jest Tams i kto go utrzymuje?

AutorVoxylDev
KategoriaAgent Platform
Gwiazdki6
Źródłohttps://github.com/VoxylDev/TAMS
Frameworksopenai · anthropic · ollama
Protocolsmcp · rest

Popularne alternatywy w agent_platform

Amazon Bedrock AgentCore
59.9/100 · C
pulsemcp
clawhub
61.8/100 · C+
github
ag2ai/fastagency
60.2/100 · C+
github
Tiledesk/tiledesk-dashboard
58.5/100 · C
github
gaoyangz77/easyclaw
58.3/100 · C
github

What Is Tams?

Tams is a software tool in the agent_platform category: TAMS is a biologically-inspired memory system for AI agents.. It has 6 GitHub stars. Nerq Trust Score: 62/100 (C).

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 Tams's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Tams performs in each:

The overall Trust Score of 62.2/100 (C) 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 Tams?

Tams is commonly evaluated by:

How to read the signals: Tams's measured signals (bezpieczeństwo 0/100, konserwacja 1/100, dokumentacja 1/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 Tams'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's 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 Tams's dependency tree.
  3. Opinia permissions — Understand what access Tams requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Tams 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=TAMS
  6. Sprawdź license — Confirm that Tams'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 Tams

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

Data handling

Understand how Tams 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 Tams'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 Tams. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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

Best Practices for Using Tams Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for bezpieczeństwo advisories

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

Situations That Warrant Independent Review of Tams

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

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

How Tams Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among agent_platform tools, the average Trust Score is 62/100. Tams's score of 62.2/100 is above the category average of 62/100.

This positions Tams favorably among agent_platform tools. While it outperforms the average, there is still room for improvement in certain trust wymiarów.

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 Tams 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, Tams'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 Tams's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=TAMS&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 Tams are strengthening or weakening over time.

Tams vs Alternatywy

In the agent_platform category, Tams scores 62.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Kluczowe wnioski

Często zadawane pytania

Czy Tams jest bezpieczny?
TAMS z wynikiem zaufania Nerq 62.2/100 (C). Najsilniejszy sygnał: konserwacja (1/100). Wynik oparty na Bezpieczeństwo (0/100), Konserwacja (1/100), Popularność (0/100), Dokumentacja (1/100).
Jaki jest wynik zaufania Tams?
TAMS: 62.2/100 (C). Wynik oparty na Bezpieczeństwo (0/100), Konserwacja (1/100), Popularność (0/100), Dokumentacja (1/100). Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=TAMS
Jakie są bezpieczniejsze alternatywy dla Tams?
W kategorii Agent Platform, higher-rated alternatives include Amazon Bedrock AgentCore (60/100), clawhub (62/100), ag2ai/fastagency (60/100). TAMS scores 62.2/100.
Jak często aktualizowana jest ocena bezpieczeństwa Tams?
Nerq recomputes Tams's trust score as new data becomes available. Current: 62.2/100 (C). API: GET nerq.ai/v1/preflight?target=TAMS
Czy mogę używać Tams w środowisku regulowanym?
Tams: 62.2/100 (C). 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ść