updated 2026-11-02 12:09 UTC

typedai

Repository Website

TypeScript AI platform with AI chat, Autonomous agents, Software developer agents, chatbots and more

Coding Agents TypeScript Listed MIT

Is typedai safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.3 / 10
Provenance None
Signed commits 0%
Last push 315d ago
Compare typedai

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: typedai scores 27.1/100 (Grade D), ranked #1351 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.3/10; recent commits are unsigned; last pushed 2025-12-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How typedai could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships typedai and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/TrafficGuard/typedai, MIT, last pushed 2025-12-22. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.3/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. typedai is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 2.3/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues typedai’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How typedai compares in Coding Agents

  1. #72 10x 30.3 +3.2
  2. #73 PearAI 27.2 +0.1
  3. #74 typedai 27.1 this agent
  4. #75 Devika 26.2 −0.9
  5. #76 Plandex 23.5 −3.6

Bars show each HVTrust score; the tick marks typedai’s 27.1.

Where the 27.1 comes from

HVTrust dimensions vs the Coding Agents average

27.1 / 100 · 100.0% confidence

typedai Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.9 / 25
6.3 below avg 9.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.8 below avg 14.8
AdoptionLog-scaled stars · package downloads
7.4 / 20
4.7 below avg 12.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1322 → #1333)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 315 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Coding Agents Report missing data
27.6
Activity sub-score · out of 100
#74
In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-02 12:09 UTC · Repo last pushed 315 days ago — may be stale

Rank Trend

2026-09-29 2026-11-02

Activity & Reach

Stars
1.2k
Forks
90
Last Push
2025-12-22
315 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
8
Rank Change
=
was #1351

Analysis

Activity Inputs

27.6 / 100
StarsRepository reach
18.5 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.1 / 20

Common questions about typedai

Public trust evidence for typedai is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does typedai publish package provenance?
No published build provenance is currently detected for typedai. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does typedai have an OpenSSF Scorecard?
typedai has an OpenSSF Scorecard score of 2.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is typedai actively maintained?
Stale. The repository has not been pushed to in 315 days. Consider whether the project is still being maintained.
What license does typedai use?
typedai ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are typedai's commits signed?
0% of the last 100 commits to typedai are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
11 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • code
  • database
  • search
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to typedai's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Groq, Mistral AI, OpenAI, OpenRouter, Perplexity, Postgres, SerpAPI, xAI Grok
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain typedai?

For maintainers

HVTrust scores typedai from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 15HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1322 → #1333)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Groq, Mistral AI, OpenAI, OpenRouter, Perplexity, Postgres, SerpAPI, xAI Grok
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank dropped 245 spots (#1060 → #1305)
2026-09-23
HVTrust Changed
HVTrust up 4.0pts (23.1 → 27.1)
2026-09-22
Newly Listed
First tracked at rank #1060
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 10 spots (#1282 → #1292)
2026-09-06
Rank Moved
Rank dropped 12 spots (#1262 → #1274)
2026-09-05
Rank Moved
Rank dropped 14 spots (#1248 → #1262)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1232 → #1248)
2026-09-03
Rank Moved
Rank dropped 41 spots (#1191 → #1232)
2026-09-02
Rank Moved
Rank dropped 36 spots (#1155 → #1191)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1114 → #1155)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1083 → #1114)
2026-08-30
Scorecard Added
OSSF Scorecard: 2.3/10
2026-08-30
Rank Moved
Rank rose 233 spots (#1316 → #1083)
2026-08-30
HVTrust Changed
HVTrust up 18.2pts (8.9 → 27.1)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1283 → #1308)
2026-08-10
Rank Moved
Rank dropped 79 spots (#1204 → #1283)
2026-08-08
Rank Moved
Rank dropped 682 spots (#522 → #1204)
2026-08-06
Rank Moved
Rank dropped 54 spots (#468 → #522)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 27.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/typedai.svg)](https://hvtracker.net/agents/typedai)
HTML:
<a href="https://hvtracker.net/agents/typedai"><img src="https://hvtracker.net/badge/typedai.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON