UTA v1.0.0 — full status report: 96 articles, 2,276 NPM downloads, here's what's next

Correction (Aug 25): Earlier version of this article misnamed the project as "ATC/1.0 — Agent Trust Card Protocol." That was wrong. ATC is one of 8 adapter formats UTA supports — not the project name. This version corrects that throughout.

The project is Universal Trust Adapter (UTA) v1.0.0. ATC is one of 8 formats it translates between (the others: EAT-AI, ZTA, A2A, MCP Card, W3C VC, OAuth, SPIFFE). The canonical schema is Universal Trust Schema (UTS) v2.0.0.

Two months in. Here's the honest numbers, then what's next.

The numbers (as of Aug 25, 2026)

NPM packages

All packages mirrored automatically by jsDelivr CDN and unpkg CDN.

Dev.to

• 96 articles published since July 2
• 26 reactions accumulated
• 44 comments received from 15 different developers
• 5 batched response articles published (responding to all 32 actionable comments)
• 258 minutes total reading time

Top commenters by engagement:

• @anp2network (6 comments) — most technically rigorous, found the JCS bug
• @mads_hansen (6 comments) — conexor.io, runtime policy angle
• @wrencalloway (4 comments) — wcalloway.substack.com, tool-description-poisoning
• @topstar_ai (3 comments) — production LLM systems, asked about collaboration
• @neelagiri65 (2 comments) — pushed for honest per-layer catch counts

GitHub

• alicelabs-llc org: 21 repos, 6 stars, 1 fork
• Most starred: sam-gov-types (3 stars), samgov-sdk (2 stars), Scraper (1 star)
• Personal account: flagged by abuse-detection (ticket #4658791 open 2 weeks — still unresolved, SMS verification completed)
• UTA canonical repo: https://github.com/alicelabs-llc/universal-trust-adapter (publicly accessible)

marketnow.site (AliceLabs-owned)

• HTTP 200 active
• Serving tarballs directly: /uta-packages/marketnow-uts-2.0.0.tgz etc.
• Multi-source installer: /install.sh (tries NPM → jsDelivr → unpkg → marketnow.site → GitHub)
• Resilience manifest: /resilience.json

What UTA actually is

Universal Trust Adapter (UTA) is the project. It's the USB-C of agent trust — translates between 8 trust credential formats via a canonical Universal Trust Schema (UTS).

The 8 formats UTA translates between:

1. ATC (Agent Trust Card — AliceLabs)
2. EAT-AI (IETF RFC 9421)
3. ZTA (Anthropic Zero-Trust Agent)
4. A2A Agent Card (Google/AAIF)
5. MCP Server Card (Anthropic)
6. W3C Verifiable Credentials
7. OAuth/OIDC
8. SPIFFE SVID

The 12-stage verification pipeline uses Ed25519 (RFC 8032) signatures over RFC 8785 JCS canonicalization, with domain separation across 7 distinct signature domains to prevent cross-context reuse.

What worked

1. Writing in public. 96 articles in 8 weeks. The 44 comments pushed the spec harder than 6 months of private iteration would have. @anp2network's first comment (the JCS replacer bug) caught a real cryptographic flaw I'd shipped to production.

2. Multi-channel distribution. When GitHub flagged my account two weeks ago, the 5-channel setup meant the project kept working. NPM downloads continued at the same rate. No user-visible disruption.

3. Responding to every technical comment. Even when the comment was sharp (anp2network called the spec "a private result that weighs about as much as any other assertion nobody can re-derive"), engaging with the substance produced the highest-value feedback. The test vectors only exist because anp2network publicly shamed me into publishing the bytes.

4. Publishing the test CA private key. Sounds counterintuitive but it's the only way to make a crypto spec truly verifiable across languages. Anyone can re-derive the signatures in Python, Go, or Rust.

What didn't work

1. Relying on a single GitHub account. When the personal account got flagged, 55 public repos instantly returned HTTP 404. Should have moved to the org earlier.

2. NPM package metadata still points to the flagged account. Without an NPM publish token in the build environment, I couldn't republish packages with updated repository.url. The tarballs are byte-identical and downloadable, but the "Repository" link on npmjs.com is broken.

3. "8 layers of security" framing. The honest version is "8 layers, 2 of which actually caught things." The article should have led with per-layer catch counts, not layer count.

4. Naming confusion between ATC and UTA. ATC is one of 8 adapters in UTA, but my early articles presented ATC as if it were the project. The repo name (universal-trust-adapter) was always right; the article framing was wrong. Fixed in this article.

5. Not having a Hacker News / Reddit presence. Dev.to reaches the Dev.to audience, but the broader security / AI / cryptography communities don't read Dev.to. Should have cross-posted from day 1.

Where I'm publishing next

Based on the gap analysis, the project needs presence on platforms where the security / AI / MCP communities actually hang out:

• Reddit: r/MCP, r/LocalLLaMA, r/cybersecurity, r/webdev
• Hacker News: Show HN submission for UTA v1.0.0
• Hashnode: cross-posting articles
• LinkedIn: B2B audience for enterprise security
• Twitter/X: threads for developer discovery
• Discord communities: Anthropic, MCP, Cursor, Cline, Continue, Aider servers
• MCP marketplaces: Smithery.ai, Glama.ai, PulseMCP, mcp.so

If you're in any of those communities and want to vouch for the project, that's the highest-value thing anyone can do right now.

What's next on the technical side

1. Multi-sig for high-value agents — attestation.signature becomes an array, verifier requires N-of-M. Spec'd but not implemented.

2. Runtime tool-catalog pinning — the fix for the tool-description-poisoning attack @wrencalloway flagged. Pin catalog at approval, block at runtime if catalog changes.

3. Behavior-based detection layer — post-exec filter that inspects actual tool results, not just pre-call signatures.

4. More test vectors — the 5 current vectors cover the obvious failure classes (expired, tampered, wrong-ca-key, minimal-valid, capability-samples). Need edge cases: nested objects deeper than 2 levels, unicode payloads, large card sizes, multi-sig.

5. NPM republish with correct repository.url — once I have an NPM publish token, republish all 7 packages with repository.url pointing to alicelabs-llc instead of the flagged personal account.

6. Cross-language SDKs — currently Node.js only. Python, Go, Rust SDKs to be published from the same source tree.

The honest ask

The project is at the inflection point where it needs more reviewers, not more features. If you're a security researcher, a cryptography implementer, or an MCP server author:

• Run your independent verifier against the test vectors: https://github.com/alicelabs-llc/universal-trust-adapter/tree/main/marketnow/docs/atc-spec/test-vectors
• Post disagreements (or confirmations) — both are equally useful
• If you find a bug, I'll triage and fix the same day

Repo: https://github.com/alicelabs-llc/universal-trust-adapter
NPM: marketnow-mcp@1.10.0 (958/mo) and agent-trust-card@1.1.1 (518/mo)
Install: curl -fsSL https://marketnow.site/install.sh | bash

— Edison Flores, AliceLabs LLC