OASB
Jul 13|OASB v0.4.0 on npm: library entry point, reproducible installs, contribution guide
All updates
OASB / Open Agent Security Benchmarkv0.4.0 · Apache-2.0 · OpenA2A

97,127 hosts scanned.
One benchmark emerged.

OASB is the open standard for AI agent security: compliance controls, behavioral governance, and a reproducible tool evaluation, built from real-world data.

$git clone https://github.com/opena2a-org/oasb
StatusOpen standard
LicenseApache-2.0
MaintainerOpenA2A
Version0.4.0
AIAgentIdentityAuthorizationInputOutputCredentialsSupply ChainAgent-to-AgentMemoryOperationsMonitoringL1L2L3
L1 Essential
L2 Standard
L3 Hardened

Internet-wide scan data

The current state of AI agent security

HackMyAgent scanned the public internet for exposed AI agent infrastructure. The results informed which OASB controls matter most.

97,127

Hosts discovered

11,192

Hosts scanned

1,594

Vulnerable

1,190

CLAUDE.md exposed

645

MCP tools exposed

5,042

Outdated endpoints

Read the full research report

Reference results

F1, precision and false-positive rate withdrawn. Recall stands, with its denominator.

This section previously published an F1 score and a false-positive rate for the HackMyAgent pipeline. Those figures are withdrawn. 3,704 of the 3,881 benign samples were labeled benign by the rule verdict='warning' AND overall_score >= 70 as reported by HackMyAgent itself, so anything the scanner would have flagged was excluded from the benign class by construction and a near-zero false-positive rate was guaranteed before any scan ran. A scanner cannot be graded against labels it produced.

That reasoning covers every metric which reads the benign class. It does not cover recall, which reads only the malicious class, and the first version of this notice withdrew recall anyway. That was an error in the correction, fixed on 2026-08-09. Recall is 223 of 270, or 82.6%, measured on attack fixtures we authored ourselves. Read with the self-labeled samples scored too it is 47.3% (234 of 495), and the benchmark page shows both, plus the split by source.

We are re-measuring on corpora we neither own nor labeled, and will republish only figures a third party can reproduce without our cooperation. No comparative claim is made until then.

Corpus and methodologyDataset: v2.0 / F1, precision, FPR withdrawn 2026-08-09

Your security team will ask what standard you are using.

Send them here.

OASB Eval

Verify your agent's security

Check your agent against the OASB-1 controls with the reference implementation. Read the docs for CI/CD integration and other adapters.

$npx hackmyagent secure --benchmark oasb-1

Adopt and contribute

Open standard / Apache-2.0

OASB is developed in the open and welcomes co-authors and adopters. Run the benchmark against your product, submit results, or propose new controls and scenarios.

01

Submit an adapter

Implement the SecurityProductAdapter interface and run the same scorecard. Independent submissions are shown alongside the reference adapter.

Adapter interface
02

Map to the controls

Assess your agent against the 46 OASB-1 compliance controls and the 72 OASB-2 governance controls.

View the controls
03

Propose changes

Open an issue or pull request to refine the controls, scenarios, or scoring methodology.

OASB on GitHub

Cite this standard

v0.4.0

Plain

OpenA2A. (2026). OASB: Open Agent Security Benchmark (v0.4.0). https://oasb.ai

BibTeX

@misc{oasb2026,
  title   = {OASB: Open Agent Security Benchmark},
  author  = {OpenA2A},
  year    = {2026},
  version = {0.4.0},
  url     = {https://oasb.ai}
}