← Leaderboard
8.5 L4

Deno V2

Native Assessed · Docs reviewed · Mar 27, 2026 Confidence 0.59 Last evaluated Mar 27, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Deno V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 27, 2026

Freshness

Updated 2026-03-27T03:16:09.649+00:00

Mar 27, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.7
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.2
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.5

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Deno: Comprehensive Agent-Usability Assessment

Docs-backed

Deno is a modern rethink of the Node.js model: secure by default (explicit permission flags for file/network access), built-in TypeScript without compilation config, web-standard APIs, and a built-in standard library. Deno KV and Deno Deploy extend it to a full edge platform. Confidence is docs-derived.

keel-expansion Mar 27, 2026

Deno: API Design & Integration Surface

Docs-backed

The runtime surface covers web-standard APIs (fetch, Request, Response, WebSocket, etc.), Deno-specific APIs (Deno.readFile, Deno.serve, etc.), npm compatibility, and Deno KV for edge-local key-value storage. The standard library covers HTTP, path, testing, encoding, and more.

keel-expansion Mar 27, 2026

Deno: Auth & Access Control

Docs-backed

Access control is capability-based: explicit flags (--allow-net, --allow-read, --allow-env) are required for external access. This makes Deno programs more auditable than Node.js for security-conscious deployments. Deno Deploy uses project tokens for deployment.

keel-expansion Mar 27, 2026

Deno: Error Handling & Operational Reliability

Docs-backed

Operationally, Deno is designed for correctness and security. The permission model prevents accidental data exfiltration but requires deliberate flag configuration. npm compatibility is now comprehensive enough for most production use cases.

keel-expansion Mar 27, 2026

Deno: Documentation & Developer Experience

Docs-backed

Documentation at docs.deno.com is excellent and improving rapidly. The standard library reference and Deno Deploy guides are thorough. Developer experience is strong for TypeScript developers who value security-by-default and web-standard APIs.

keel-expansion Mar 27, 2026

Use in your agent

mcp
get_score ("deno-v2")
● Deno V2 8.5 L4 Native
exec: 8.7 · access: 8.2

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.5 / 10.0

Alternatives

No alternatives captured yet.