typedai

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

Coding Agents TypeScript Grade D Listed MIT
27.1/100
Rank #1305 of 1328
Compare typedai

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2025-12-22 · 270d ago
Recent change
No recent signal change

Is typedai safe? typedai scores 27.1/100 (Grade D), ranked #1305 of 1328 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 →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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 270 days ago. Fresh activity helps separate stable projects from stale ones.
27.6
Activity sub-score · out of 100
#69

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-09-18 13:03 UTC · Repo last pushed 270 days ago — may be stale

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars
1.2k
Forks
91
Last Push
2025-12-22
270 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
8
Rank Change
▼1
was #1304

Analysis

HVTrust Dimensions vs Coding Agents

27.1 / 100 · 100.0% confidence

typedai Coding Agents average (72 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.9 / 25
6.1 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.9 below avg 14.9
AdoptionLog-scaled stars · package downloads
7.4 / 20
4.8 below avg 12.2

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

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.3 / 10
OpenSSF Scorecard · scanned Sep 5, 2026
Signed Commits
0%
of last 100 commits verified
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

Is typedai safe?

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 270 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

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.

Reputation Timeline

Signal history
Rank 13Listed 1HVTrust 1Scorecard 1
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)
2026-08-03
Newly Listed
First tracked at rank #468

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.3 · Raw JSON