Is T0 Safe?

T0 — Nerq Trust Score 59.2/100 (D grade). Based on analysis of 4 trust dimensions, it is has notable safety concerns. Last updated: 2026-05-07.

Use T0 with some caution. T0 is a software tool with a Nerq Trust Score of 59.2/100 (D), based on 4 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-07. Machine-readable data (JSON).

Is T0 safe?

CAUTION — T0 has a Nerq Trust Score of 59.2/100 (D). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → T0 Privacy Report →

What is T0's trust score?

T0 has a Nerq Trust Score of 59.2/100, earning a D grade. This score is based on 4 independently measured dimensions including security, maintenance, and community adoption.

Compliance
87
Maintenance
0
Documentation
0
Popularity
0

What are the key security findings for T0?

T0's strongest signal is compliance at 87/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Compliance: 87/100 — covers 45 of 52 jurisdictions
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 83 stars on huggingface search

What is T0 and who maintains it?

Authorbigscience
CategoryAi
Stars83
Sourcehttps://huggingface.co/bigscience/T0
Protocolshuggingface_api

Regulatory Compliance

EU AI Act Risk ClassMINIMAL
Compliance Score87/100
JurisdictionsAssessed across 52 jurisdictions

Popular Alternatives in AI

MycroftAI/mycroft-core
67.5/100 · B-
github
Holo1-7B
58.3/100 · D
huggingface_full
Ovis2-1B
60.4/100 · C
huggingface_author2
ALIA-40b
59.2/100 · D
huggingface_w2
Ouro-2.6B-Thinking
59.2/100 · D
huggingface_new

What Is T0?

T0 is a software tool in the AI category: T0 is an AI agent based on large language models.. It has 83 GitHub stars. Nerq Trust Score: 59/100 (D).

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

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

The overall Trust Score of 59.2/100 (D) 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 T0?

T0 is designed for:

Risk guidance: T0 is suitable for development and testing environments. Before production deployment, conduct a thorough review of its security posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify T0'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 T0's dependency tree.
  3. Review permissions — Understand what access T0 requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run T0 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=T0
  6. Review the license — Confirm that T0'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 T0

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

Data handling

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

Update frequency

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

Third-party integrations

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

T0 and the EU AI Act

T0 is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.

Best Practices for Using T0 Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid T0?

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

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

How T0 Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among AI tools, the average Trust Score is 62/100. T0's score of 59.2/100 is near the category average of 62/100.

This places T0 in line with the typical AI tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.

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

T0 vs Alternatives

In the AI category, T0 scores 59.2/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 T0 collect?

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

Is T0 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: T0 Security Report

How we calculated this score

T0's trust score of 59.2/100 (D) 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 07, 2026. Data version: 1.0.

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

Frequently Asked Questions

Is T0 Safe?
Use with some caution. T0 with a Nerq Trust Score of 59.2/100 (D). Strongest signal: compliance (87/100). Score based on Maintenance (0/100), Popularity (0/100), Documentation (0/100).
What is T0's trust score?
T0: 59.2/100 (D). Score based on Maintenance (0/100), Popularity (0/100), Documentation (0/100). Compliance: 87/100. Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=T0
What are safer alternatives to T0?
In the Ai category, higher-rated alternatives include MycroftAI/mycroft-core (68/100), Holo1-7B (58/100), Ovis2-1B (60/100). T0 scores 59.2/100.
How often is T0's safety score updated?
Nerq continuously monitors T0 and updates its trust score as new data becomes available. Current: 59.2/100 (D), last verified 2026-05-07. API: GET nerq.ai/v1/preflight?target=T0
Can I use T0 in a regulated environment?
T0 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