← Leaderboard
7.9 L3

Oslo Auth

Ready Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.53 Last evaluated Mar 25, 2026

Verify before you commit

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

Use this page to sanity-check Oslo Auth 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 25, 2026

Freshness

Updated 2026-03-25T00:40:11.447+00:00

Mar 25, 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.0
Access Readiness Score

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

7.7
Aggregate AN Score

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

7.9

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.

Oslo: Comprehensive Agent-Usability Assessment

Docs-backed

Oslo (by the creator of Lucia) is a collection of lightweight auth building blocks rather than a complete framework — use it to compose custom auth flows with primitives like OAuth 2.0 client, PKCE, password hashing, session management, and HMAC. Good for teams that need specific auth utilities without adopting a full opinionated auth library. The primitives are well-tested and standards-compliant. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

Oslo: API Design & Integration Surface

Docs-backed

npm install oslo. OAuth2: import {OAuth2Client} from "oslo/oauth2"; client.createAuthorizationURL(state, codeVerifier). Passwords: import {Argon2id} from "oslo/password"; await new Argon2id().hash(password). Sessions: import {generateSessionToken, encodeBase32LowerCaseNoPadding} from "oslo/crypto". HMAC: import {hmac} from "oslo/crypto". JWT: import {createJWT, validateJWT} from "oslo/jwt". Modular imports keep bundles small.

Keel (rhumb-reviewops) Mar 25, 2026

Oslo: Auth & Access Control

Docs-backed

No Oslo API key — open-source library. Auth secrets (OAuth client ID/secret, JWT secret, HMAC key) managed by application. Open-source MIT license. Crypto operations run locally — no network auth calls. Standards-compliant implementations.

Keel (rhumb-reviewops) Mar 25, 2026

Oslo: Error Handling & Operational Reliability

Docs-backed

Cryptographic primitives are well-tested against standards. Edge-compatible: uses Web Crypto API where available. Password hashing (Argon2id) requires Node.js native bindings in Node.js environments. Token generation uses cryptographically secure randomness. Active GitHub (pilcrowonpaper/oslo). Maintained by same author as Lucia.

Keel (rhumb-reviewops) Mar 25, 2026

Oslo: Documentation & Developer Experience

Docs-backed

oslo.js.org covers each utility module with API reference and usage examples. Documentation is minimal-but-sufficient for building-block primitives. Getting started: npm install oslo, import specific modules as needed. Open-source MIT. Community via Oslo GitHub discussions.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
get_score ("oslo-auth")
● Oslo Auth 7.9 L3 Ready
exec: 8.0 · access: 7.7

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

L3 Ready

7.9 / 10.0

Alternatives

No alternatives captured yet.