Talorys
Your personal AI agent in your own Cloudflare account. Chat, memory, tasks, notes and scheduled reminders, deployed with one command: npx create-talorys@latest. Free-tier friendly, single-user, no telemetry.
Is Talorys safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Talorys
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: Talorys scores 41.1/100 (Grade D), ranked #1194 of 1387 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 89% of recent commits are signed; no published advisory affects its latest release (create-talorys); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How Talorys 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +36.9 → 78.0 B · #17 of 134
- Publish build provenance for its packagesnpm publish --provenance from CI +32.7 → 73.8 B · #22 of 134
Chain of custody
Scanners check what the code says. This traces who ships Talorys and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/rociiu/talorys, MIT, last pushed 2026-11-10. 89% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Linked, not attested
- npm create-talorys Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: create-talorys 0.1.8. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Talorys.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Talorys’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.
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 Talorys compares in Agent Frameworks
- #108 ControlFlow 44.4 +3.3
- #109 OpenFang 43.3 +2.2
- #110 Talorys 41.1 this agent
- #111 PocketFlow 40.2 −0.9
- #112 omniclaw 39.0 −2.1
Bars show each HVTrust score; the tick marks Talorys’s 41.1.
Where the 41.1 comes from
HVTrust dimensions vs the Agent Frameworks average
41.1 / 100 · 67.0% confidenceTalorys Agent Frameworks average (134 agents)
Quick Trust Read
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 →
Activity & Reach
Analysis
Activity Inputs
78.0 / 100Common questions about Talorys
Does Talorys publish package provenance?
Does Talorys have an OpenSSF Scorecard?
Is Talorys actively maintained?
What license does Talorys use?
Are Talorys's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Talorys?
For maintainers
HVTrust scores Talorys 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/talorys)
<a href="https://hvtracker.net/agents/talorys"><img src="https://hvtracker.net/badge/talorys.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON