Titen

Agent memory that needs no API key, no LLM, and no embedding provider. One command on Bun and it is serving MCP over std

Memory & Knowledge TypeScript Grade C Listed Apache-2.0
57.9/100
Rank #516 of 1320
Compare Titen

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-30 · 5d ago
Recent change
Rank +6

Is Titen safe? Titen scores 57.9/100 (Grade C), ranked #516 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 10% of recent commits are signed; last pushed 2026-08-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 13 spots (#503 → #516)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-03
Rank Moved
Rank dropped 38 spots (#465 → #503)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
56.0
Activity sub-score · out of 100
#32

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

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
12
Forks
0
Last Push
2026-08-30
5 days ago
Commits (4 wk)
102
Downloads (7d)
388
npm
HN mentions (30d)
Open Issues
1
Rank Change
▼13
was #503

Analysis

HVTrust Dimensions vs Memory & Knowledge

57.9 / 100 · 100.0% confidence

Titen Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
6.4 below avg 11.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
1.3 below avg 12.9
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
2.1 above avg 17.6
AdoptionLog-scaled stars · package downloads
6.1 / 20
7.2 below avg 13.3

Activity Inputs

56.0 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.6 / 10
OpenSSF Scorecard · scanned Sep 3, 2026
Signed Commits
10%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 4
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 9

Is Titen safe?

Titen has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Titen publish package provenance?
No published build provenance is currently detected for Titen. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Titen have an OpenSSF Scorecard?
Titen has an OpenSSF Scorecard score of 3.6/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 Titen actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does Titen use?
Titen ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Titen's commits signed?
10% of the last 100 commits to Titen 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
high confidence
Implemented
Titen appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Titen'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-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared

Maintain Titen?

For maintainers

HVTrust scores Titen 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 8Listed 1HVTrust 1Grade 1Scorecard 1Surface 1
2026-09-04
Rank Moved
Rank dropped 13 spots (#503 → #516)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-03
Rank Moved
Rank dropped 38 spots (#465 → #503)
2026-09-02
Rank Moved
Rank dropped 14 spots (#451 → #465)
2026-09-01
Rank Moved
Rank dropped 13 spots (#438 → #451)
2026-08-31
Rank Moved
Rank dropped 34 spots (#404 → #438)
2026-08-30
Rank Moved
Rank rose 16 spots (#420 → #404)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 299 spots (#708 → #409)
2026-08-26
HVTrust Changed
HVTrust up 22.9pts (35.2 → 58.1)
2026-08-16
Rank Moved
Rank dropped 13 spots (#693 → #706)
2026-08-10
Newly Listed
First tracked at rank #696

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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