AbsoluteJS

@absolutejs/agent-conformance

@absolutejs/agent-conformancev0.15.1betaAI

Provider-neutral adversarial conformance for agent security plus A2A, MCP, Arazzo, and WebMCP standards.

#Installation

BASH
bun add @absolutejs/agent-conformance

#Capabilities

Overview

Provider-neutral adversarial test runners for AI agent security boundaries. Adapters expose a tiny harness; the package attacks it with replay, concurrent maximum-use races, confused-deputy identity, scope escalation, lookalike URL origins, mutated approved inputs, denied lease issuance, failed-execution replay, and task-owner isolation.

The runners return data rather than depending on a test framework, so they work inside Bun test, Vitest, Jest, CI scripts, or provider certification jobs.

The effect-adapter suites separately prove global certification, descriptor-driven reconciliation setup, tenant-scoped installation, and execution-time behavior. The execution suite verifies that authorization happens before secret resolution, only installed aliases are resolved, tenant/effect/destination/idempotency context reaches the driver, driver capabilities match the certified descriptor, and unknown provider outcomes enter durable quarantine.

Show 9 more

The effect-evidence suite verifies that provider signatures are checked before persistence, duplicate deliveries remain single-copy while reconciliation can resume after a crash, retained delivery identities cannot be rebound across effects or tenants, and only normalized evidence crosses the durable boundary.

The reconciliation-runtime suite proves that scheduled provider queries authorize before resolving credentials, use a cross-replica lease, retain only normalized evidence, reduce failures to safe health codes, and keep an operator-triggered tenant run from querying another tenant's effects. It also proves that reference-gated queries stop before credential resolution when no exact provider resource is retained and that stale attempts cannot quarantine a newer lease.

Version 0.3 adds discovery signature/search, durable runtime recovery/budget, provenance/taint, scoped memory, and verified inbox suites. Passing reports can be combined into a deterministic, optionally signed absolutejs-agent-first-1 certification artifact and linked from an agent's public discovery descriptor.

Version 0.4 adds provider-neutral conformance harnesses for A2A 1.0, MCP 2025-11-25, Arazzo 1.1, and the July 2026 WebMCP draft. They test protocol negotiation, task/session isolation, required extensions, unsafe callback URLs, dependency ordering, policy-before-effect, unsupported-feature atomicity, input validation, metadata poisoning, cross-origin exposure, and abort cleanup.

Implement only the harnesses relevant to your package:

ActionConformanceHarness for approval binding and execution leases.

CapabilityConformanceHarness for credential grants, delegations, spend

mandates, or other bounded capabilities.

TaskConformanceHarness for durable task ownership and cancellation.

Rejections must name their control

Every scenario that expects a rejection asserts on a token from the control's own vocabulary — "lease", "owner", "private", "host", "replay", "denied", "bound", "scope", "actor", "destination". Your implementation's error message has to contain it.

This is a real obligation, and it exists because the alternative is worse. A scenario that accepts _any_ rejection passes on failures that have nothing to do with the control it claims to test:

Both throw. Before 0.15.0 both satisfied the egress scenarios on any machine — so a suite meant to prove SSRF and lookalike-origin defences proved nothing, and reported a green tick while doing it. .evil.test is a reserved TLD that can never resolve, which means that scenario could not have failed for the right reason even in principle.

Show 1 more

An unnamed rejection is indistinguishable from an accident. Naming the control is what makes a pass mean something.

Outcomes

What you can build

Build on the supported package contract

Use @absolutejs/agent-conformance through its supported public entry points.

Hardening checklist

Production guidance

Make every external boundary explicitPin the deployed @absolutejs/agent-conformance version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.

Follow in order

Troubleshooting path

1
Trace from the first failed boundary
Reproduce the smallest canonical @absolutejs/agent-conformance example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.

#@absolutejs/agent-conformance quick start

Partial snippet

# @absolutejs/agent-conformance

TS
import {
  assertConformance,
  runCapabilityConformance,
} from "@absolutejs/agent-conformance";

const report = await runCapabilityConformance(() => yourHarness());
assertConformance(report); // throws with the complete report when any case fails

#@absolutejs/agent-conformance quick start 2

Partial snippet

# @absolutejs/agent-conformance

TS
import {
  runA2aConformance,
  runArazzoConformance,
  runMcpConformance,
  runWebMcpConformance,
} from "@absolutejs/agent-conformance";

#Rejections must name their control

Partial snippet

Every scenario that expects a rejection asserts on a token from the control's own vocabulary — "lease", "owner", "private", "host", "replay", "denied", "bound", "scope", "actor", "destination". Your implementation's error message has to contain it.

TXT
fetch("https://api.example.com.evil.test")
  -> "Unable to connect. Is the computer able to access the url?"
fetch("https://169.254.169.254/latest")
  -> "The operation timed out."

#Public entry points

Supported entry points declared by this package manifest.

Package entry point declared in package.json.

@absolutejs/agent-conformance@absolutejs/agent-conformance/manifest@absolutejs/agent-conformance/manifest.json

#Package commands

Scripts declared by this package manifest.

bun run buildrm -rf dist && bun build src/index.ts src/manifest.ts --outdir dist --root src --sourcemap --target=bun --external @absolutejs/manifest --external @sinclair/typebox && tsc --project tsconfig.build.json && absolute-manifest emit
bun run check:packagebun run typecheck && bun run test && bun run build
bun run formatprettier --write "./**/*.{ts,json,md}"
bun run testbun test tests/
bun run typechecktsc --noEmit

#API reference

Search the declarations exported by the current package type files. Expand a symbol to inspect its source-backed signature.

52 symbols
ConformanceResulttypePermalinkSource
TS
type ConformanceResult = {
    error?: string;
    name: string;
    passed: boolean;
};
Exported from @absolutejs/agent-conformance