Ist Tams sicher?

Tams — Nerq Trust Score 62.2/100 (Note C). Bewertung basierend auf 4 independent trust signals.

Tams ist ein software tool mit einem Nerq-Vertrauenswert von 62.2/100 (C), basierend auf 4 unabhängigen Datendimensionen. Sicherheit: 0/100. Wartung: 1/100. Beliebtheit: 0/100. Daten von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Zuletzt aktualisiert: n/a. Maschinenlesbare Daten (JSON).

Ist Tams sicher?

Vertrauensbewertung im Detail — Tams has a Nerq Trust Score of 62.2/100 (C). Measured across 4 independent trust signals.

Sicherheitsanalyse → Tams Datenschutzbericht →

Was ist die Vertrauensbewertung von Tams?

Tams hat eine Nerq-Vertrauensbewertung von 62.2/100 und erhält die Note C. Diese Bewertung basiert auf 4 unabhängig gemessenen Dimensionen.

Sicherheit
0
Wartung
1
Dokumentation
1
Beliebtheit
0

Was sind die wichtigsten Sicherheitsergebnisse für Tams?

Das stärkste Signal von Tams ist wartung mit 1/100. Es wurden keine bekannten Schwachstellen erkannt.

Sicherheitsbewertung: 0/100 (schwach)
Wartung: 1/100 — geringe Wartungsaktivität
Dokumentation: 1/100 — begrenzte Dokumentation
Beliebtheit: 0/100 — 6 Sterne auf github

Was ist Tams und wer pflegt es?

AutorVoxylDev
KategorieAgent Platform
Sterne6
Quellehttps://github.com/VoxylDev/TAMS
Frameworksopenai · anthropic · ollama
Protocolsmcp · rest

Beliebte Alternativen in 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-Sternen. Nerq Trust Score: 62/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.

How Nerq Assesses Tams's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five Dimensionen. 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 (Sicherheit 0/100, Wartung 1/100, Dokumentation 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 — Überprüfen Sie das/die repository's Sicherheit policy, open issues, and recent commits for signs of active Wartung.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Tams's dependency tree.
  3. Bewertung 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. Überprüfen Sie das/die 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 Sicherheit 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. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency Sicherheit

Check Tams's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.

Update frequency

Regularly check for updates to Tams. Sicherheit 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 Konformität

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 Konformität with your Sicherheit policies.

Keep dependencies updated

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

Follow least privilege

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

Monitor for Sicherheit advisories

Subscribe to Tams's Sicherheit 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 Dimensionen.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderat 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 Wartung 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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, 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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Tams are strengthening or weakening over time.

Tams vs Alternativen

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

Wichtigste Punkte

Häufig gestellte Fragen

Ist Tams sicher?
TAMS mit einem Nerq-Vertrauenswert von 62.2/100 (C). Stärkstes Signal: wartung (1/100). Bewertung basierend auf Sicherheit (0/100), Wartung (1/100), Beliebtheit (0/100), Dokumentation (1/100).
Was ist die Vertrauensbewertung von Tams?
TAMS: 62.2/100 (C). Bewertung basierend auf Sicherheit (0/100), Wartung (1/100), Beliebtheit (0/100), Dokumentation (1/100). Bewertungen werden aktualisiert, wenn neue Daten verfügbar werden. API: GET nerq.ai/v1/preflight?target=TAMS
Was sind sicherere Alternativen zu Tams?
In der Kategorie Agent Platform, higher-rated alternatives include Amazon Bedrock AgentCore (60/100), clawhub (62/100), ag2ai/fastagency (60/100). TAMS scores 62.2/100.
Wie oft wird die Sicherheitsbewertung von Tams aktualisiert?
Nerq recomputes Tams's trust score as new data becomes available. Current: 62.2/100 (C). API: GET nerq.ai/v1/preflight?target=TAMS
Kann ich Tams in einer regulierten Umgebung verwenden?
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

Siehe auch

Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.

Wir verwenden Cookies für Analysen und Caching. Datenschutz