The dataset viewer is not available for this split.
Error code: StreamingRowsError
Exception: CastError
Message: Couldn't cast
digest: string
kind: string
path: string
payload_sha3: string
prev: string
seq: int64
ts: timestamp[s]
source: struct<git: struct<head: string, url: string, branch: string, sha_verified_from: string>>
child 0, git: struct<head: string, url: string, branch: string, sha_verified_from: string>
child 0, head: string
child 1, url: string
child 2, branch: string
child 3, sha_verified_from: string
benchmarks: list<item: struct<evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: i (... 3044 chars omitted)
child 0, item: struct<evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>, code (... 3032 chars omitted)
child 0, evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>, code_lines: int64, co (... 2961 chars omitted)
child 0, ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>
child 0, max_files: int64
child 1, max_lines: int64
child 2, min_lines: int64
child 1, code_lines: int64
child 2, command: string
child 3, counts_command: string
child 4, files_source: int64
child 5, files_tests: int64
child 6, files_total: int64
child 7, method: string
child 8, test_to_source_line_ratio: double
child 9, total_lines: int64
child 10, a_licences: list<item: string>
child 0, item: stri
...
ld 1, evidence_path: string
child 2, present: bool
child 6, rerunnable_verification: struct<detail: string, evidence_path: string, present: bool>
child 0, detail: string
child 1, evidence_path: string
child 2, present: bool
child 7, versioning: struct<detail: string, evidence_path: string, present: bool>
child 0, detail: string
child 1, evidence_path: string
child 2, present: bool
child 62, criteria_missing: list<item: null>
child 0, item: null
child 63, criteria_satisfied: int64
child 64, criteria_total: int64
child 65, framework_controls_verified: int64
child 66, ladder: string
child 67, observed_level: int64
child 68, source: string
child 69, trL9_claimed: bool
child 70, trL9_reason: string
child 1, id: string
child 2, ok: bool
child 3, status: string
child 4, title: string
root: string
sbom_written: bool
total: int64
method: struct<aggregate_rule: string, excluded: string, reproduce: string, thresholds_note: string>
child 0, aggregate_rule: string
child 1, excluded: string
child 2, reproduce: string
child 3, thresholds_note: string
platform: string
schema: string
python: string
failed: int64
version: string
passed: int64
all_passed: bool
failed_ids: list<item: null>
child 0, item: null
to
{'all_passed': Value('bool'), 'benchmarks': List({'evidence': {'ceilings': {'max_files': Value('int64'), 'max_lines': Value('int64'), 'min_lines': Value('int64')}, 'code_lines': Value('int64'), 'command': Value('string'), 'counts_command': Value('string'), 'files_source': Value('int64'), 'files_tests': Value('int64'), 'files_total': Value('int64'), 'method': Value('string'), 'test_to_source_line_ratio': Value('float64'), 'total_lines': Value('int64'), 'a_licences': List(Value('string')), 'b_licences': List(Value('string')), 'default_for_unknown_is_C': Value('bool'), 'mismatches': {}, 'observed': {'agpl3': Value('string'), 'apache2': Value('string'), 'bsd3': Value('string'), 'commons_clause': Value('string'), 'garbage': Value('string'), 'gpl3': Value('string'), 'isc': Value('string'), 'lgpl': Value('string'), 'mit': Value('string'), 'mpl2': Value('string'), 'noncommercial': Value('string'), 'proprietary': Value('string'), 'sspl': Value('string'), 'unknown_absent': Value('string')}, 'only_class_A_may_relicense': Value('bool'), 'policy_probes': {'agpl3': Value('string'), 'apache2': Value('string'), 'bsd3': Value('string'), 'commons_clause': Value('string'), 'garbage': Value('string'), 'gpl3': Value('string'), 'isc': Value('string'), 'lgpl': Value('string'), 'mit': Value('string'), 'mpl2': Value('string'), 'noncommercial': Value('string'), 'proprietary': Value('string'), 'sspl': Value('string'), 'unknown_absent': Value('string')}, 'project_licence': {'LICENSE': Value('string'), '
...
Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'qualification_environment_pinned': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'reproducible_tests': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'rerunnable_verification': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'versioning': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}}, 'criteria_missing': List(Value('null')), 'criteria_satisfied': Value('int64'), 'criteria_total': Value('int64'), 'framework_controls_verified': Value('int64'), 'ladder': Value('string'), 'observed_level': Value('int64'), 'source': Value('string'), 'trL9_claimed': Value('bool'), 'trL9_reason': Value('string')}, 'id': Value('string'), 'ok': Value('bool'), 'status': Value('string'), 'title': Value('string')}), 'failed': Value('int64'), 'failed_ids': List(Value('null')), 'method': {'aggregate_rule': Value('string'), 'excluded': Value('string'), 'reproduce': Value('string'), 'thresholds_note': Value('string')}, 'passed': Value('int64'), 'platform': Value('string'), 'python': Value('string'), 'root': Value('string'), 'sbom_written': Value('bool'), 'schema': Value('string'), 'total': Value('int64'), 'version': Value('string'), 'source': {'git': {'head': Value('string'), 'url': Value('string'), 'branch': Value('string'), 'sha_verified_from': Value('string')}}}
because column names don't match
Traceback: Traceback (most recent call last):
File "/src/services/worker/src/worker/utils.py", line 147, in get_rows_or_raise
return get_rows(
dataset=dataset,
...<4 lines>...
column_names=column_names,
)
File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
return func(*args, **kwargs)
File "/src/services/worker/src/worker/utils.py", line 127, in get_rows
rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
File "/src/services/worker/src/worker/utils.py", line 483, in safe_iter
yield from ds.decode(False) if ds.features else ds
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2951, in __iter__
for key, example in ex_iterable:
^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2461, in __iter__
for key, pa_table in self._iter_arrow():
~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2486, in _iter_arrow
for key, pa_table in self.ex_iterable._iter_arrow():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 547, in _iter_arrow
for key, pa_table in iterator:
^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 430, in _iter_arrow
for key, pa_table in self.generate_tables_fn(**gen_kwags):
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 132, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
digest: string
kind: string
path: string
payload_sha3: string
prev: string
seq: int64
ts: timestamp[s]
source: struct<git: struct<head: string, url: string, branch: string, sha_verified_from: string>>
child 0, git: struct<head: string, url: string, branch: string, sha_verified_from: string>
child 0, head: string
child 1, url: string
child 2, branch: string
child 3, sha_verified_from: string
benchmarks: list<item: struct<evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: i (... 3044 chars omitted)
child 0, item: struct<evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>, code (... 3032 chars omitted)
child 0, evidence: struct<ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>, code_lines: int64, co (... 2961 chars omitted)
child 0, ceilings: struct<max_files: int64, max_lines: int64, min_lines: int64>
child 0, max_files: int64
child 1, max_lines: int64
child 2, min_lines: int64
child 1, code_lines: int64
child 2, command: string
child 3, counts_command: string
child 4, files_source: int64
child 5, files_tests: int64
child 6, files_total: int64
child 7, method: string
child 8, test_to_source_line_ratio: double
child 9, total_lines: int64
child 10, a_licences: list<item: string>
child 0, item: stri
...
ld 1, evidence_path: string
child 2, present: bool
child 6, rerunnable_verification: struct<detail: string, evidence_path: string, present: bool>
child 0, detail: string
child 1, evidence_path: string
child 2, present: bool
child 7, versioning: struct<detail: string, evidence_path: string, present: bool>
child 0, detail: string
child 1, evidence_path: string
child 2, present: bool
child 62, criteria_missing: list<item: null>
child 0, item: null
child 63, criteria_satisfied: int64
child 64, criteria_total: int64
child 65, framework_controls_verified: int64
child 66, ladder: string
child 67, observed_level: int64
child 68, source: string
child 69, trL9_claimed: bool
child 70, trL9_reason: string
child 1, id: string
child 2, ok: bool
child 3, status: string
child 4, title: string
root: string
sbom_written: bool
total: int64
method: struct<aggregate_rule: string, excluded: string, reproduce: string, thresholds_note: string>
child 0, aggregate_rule: string
child 1, excluded: string
child 2, reproduce: string
child 3, thresholds_note: string
platform: string
schema: string
python: string
failed: int64
version: string
passed: int64
all_passed: bool
failed_ids: list<item: null>
child 0, item: null
to
{'all_passed': Value('bool'), 'benchmarks': List({'evidence': {'ceilings': {'max_files': Value('int64'), 'max_lines': Value('int64'), 'min_lines': Value('int64')}, 'code_lines': Value('int64'), 'command': Value('string'), 'counts_command': Value('string'), 'files_source': Value('int64'), 'files_tests': Value('int64'), 'files_total': Value('int64'), 'method': Value('string'), 'test_to_source_line_ratio': Value('float64'), 'total_lines': Value('int64'), 'a_licences': List(Value('string')), 'b_licences': List(Value('string')), 'default_for_unknown_is_C': Value('bool'), 'mismatches': {}, 'observed': {'agpl3': Value('string'), 'apache2': Value('string'), 'bsd3': Value('string'), 'commons_clause': Value('string'), 'garbage': Value('string'), 'gpl3': Value('string'), 'isc': Value('string'), 'lgpl': Value('string'), 'mit': Value('string'), 'mpl2': Value('string'), 'noncommercial': Value('string'), 'proprietary': Value('string'), 'sspl': Value('string'), 'unknown_absent': Value('string')}, 'only_class_A_may_relicense': Value('bool'), 'policy_probes': {'agpl3': Value('string'), 'apache2': Value('string'), 'bsd3': Value('string'), 'commons_clause': Value('string'), 'garbage': Value('string'), 'gpl3': Value('string'), 'isc': Value('string'), 'lgpl': Value('string'), 'mit': Value('string'), 'mpl2': Value('string'), 'noncommercial': Value('string'), 'proprietary': Value('string'), 'sspl': Value('string'), 'unknown_absent': Value('string')}, 'project_licence': {'LICENSE': Value('string'), '
...
Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'qualification_environment_pinned': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'reproducible_tests': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'rerunnable_verification': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}, 'versioning': {'detail': Value('string'), 'evidence_path': Value('string'), 'present': Value('bool')}}, 'criteria_missing': List(Value('null')), 'criteria_satisfied': Value('int64'), 'criteria_total': Value('int64'), 'framework_controls_verified': Value('int64'), 'ladder': Value('string'), 'observed_level': Value('int64'), 'source': Value('string'), 'trL9_claimed': Value('bool'), 'trL9_reason': Value('string')}, 'id': Value('string'), 'ok': Value('bool'), 'status': Value('string'), 'title': Value('string')}), 'failed': Value('int64'), 'failed_ids': List(Value('null')), 'method': {'aggregate_rule': Value('string'), 'excluded': Value('string'), 'reproduce': Value('string'), 'thresholds_note': Value('string')}, 'passed': Value('int64'), 'platform': Value('string'), 'python': Value('string'), 'root': Value('string'), 'sbom_written': Value('bool'), 'schema': Value('string'), 'total': Value('int64'), 'version': Value('string'), 'source': {'git': {'head': Value('string'), 'url': Value('string'), 'branch': Value('string'), 'sha_verified_from': Value('string')}}}
because column names don't matchNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
OPENZEPPELIN CONTRACTS
Anticloud-hardened packaging of the upstream project
OPENZEPPELIN_CONTRACTSin category CRYPTOCURRENCY. Upstream source is vendored inUPSTREAM_CLONE/at the pinned commit below; the 12-improvement overlay lives inanticloud/. Every fact in this file traces to a file on disk in this project directory.
Category: CRYPTOCURRENCY · Upstream: https://github.com/openzeppelin/openzeppelin-contracts · Upstream pin: cd3284fde41f1c56d19078f580a0aed751cf11d2 · Vendor: Anticloud FZ LLE
What This Project Does
A library for secure smart contract development. Build on a solid foundation of community-vetted code.
- Implementations of standards like ERC20 and ERC721.
- Flexible role-based permissioning scheme.
- Reusable Solidity components to build custom contracts and complex decentralized systems.
:mage: Not sure how to get started? Check out Contracts Wizard — an interactive smart contract generator.
OpenZeppelin Contracts uses semantic versioning to communicate backwards compatibility of its API and storage layout. For upgradeable contracts, the storage layout of different major versions should be assumed incompatible, for example, it is unsafe to upgrade from 4.9.3 to 5.0.0. Learn more at Backwards Compatibility.
Overview
Release tags
We use NPM tags to clearly distinguish between audited and non-audited versions of our package:
| Tag | Purpose | Description |
|---|---|---|
| latest | ✅ Audited releases | Stable, audited versions of the package. This is the default version installed when users run npm install @openzeppelin/contracts. |
| dev | 🧪 Final but not audited | Versions that are finalized and feature-complete but have not yet been audited. This version is fully tested, can be used in production and is covered by the bug bounty. |
| next | 🚧 Release candidates | Pre-release versions that are not final. Used for testing and validation before the version becomes a final dev or latest release. |
Installation
Hardhat (npm)
$ npm install @openzeppelin/contracts
→ Installs the latest audited release (latest).
$ npm install @openzeppelin/contracts@dev
→ Installs the latest unaudited release (dev).
Foundry (git)
When installing via git, it is a common error to use the
masterbranch. This is a development branch that should be avoided in favor of tagged releases. The release process involves security measures that themasterbranch does not guarantee.
Foundry installs the latest version initially, but subsequent
forge updatecommands will use themasterbranch.
$ forge install OpenZeppelin/openzeppelin-contracts
Add @openzeppelin/contracts/=lib/openzeppelin-contracts/contracts/ in remappings.txt.
Usage
Once installed, you can use the contracts in the library by importing them:
pragma solidity ^0.8.20;
import {ERC721} from "@openzeppelin/contracts/token/ERC721/ERC721.sol";
contract MyCollectible is ERC721 {
constructor() ERC721("MyCollectible", "MCO") {
}
}
If you're new to smart contract development, head to Developing Smart Contracts to learn about creating a new project and compiling your contracts.
To keep your system secure, you should always use the installed code as-is, and neither copy-paste it from online sources nor modify it yourself. The library is designed so that only the contracts and functions you use are deployed, so you don't need to worry about it needlessly increasing gas costs.
Learn More
The guides in the documentation site will teach about different concepts, and how to use the related contracts that OpenZeppelin Contracts provides:
- Access Control: decide who can perform each of the actions on your system.
- Tokens: create tradeable assets or collectibles for popular ERC standards like ERC-20, ERC-721, ERC-1155, and ERC-6909.
- Utilities: generic useful tools including non-overflowing math, signature verification, and trustless paying systems.
The full API is also thoroughly documented, and serves as a great reference when developing your smart contract application. You can also ask for help or follow Contracts' development in the community forum.
Finally, you may want to take a look at the guides on our blog, which cover several common use cases and good practices. The following articles provide great background reading, though please note that some of the referenced tools have changed, as the tooling in the ecosystem continues to rapidly evolve.
- [The Hit
(excerpt; full text in UPSTREAM_CLONE/)
Quoted from the upstream README.md file in UPSTREAM_CLONE/.
Project-specific facts detected in this directory:
- Ecosystem: Node.js / npm (manifests: package.json, package-lock.json; scanned in UPSTREAM_CLONE)
- Top-level source layout:
audits/,contracts/,fv/,hardhat/,lib/,scripts/,test/ - Upstream commit pinned for this packaging:
cd3284fde41f1c56d19078f580a0aed751cf11d2
Installation
- Implementations of standards like ERC20 and ERC721.
- Flexible role-based permissioning scheme.
- Reusable Solidity components to build custom contracts and complex decentralized systems.
:mage: Not sure how to get started? Check out Contracts Wizard — an interactive smart contract generator.
OpenZeppelin Contracts uses semantic versioning to communicate backwards compatibility of its API and storage layout. For upgradeable contracts, the storage layout of different major versions should be assumed incompatible, for example, it is unsafe to upgrade from 4.9.3 to 5.0.0. Learn more at Backwards Compatibility.
Section quoted from the upstream readme. Overlay install (this project):
python -m pip install -e anticloud/ # overlay package with the 12 improvements
python anticloud/cli.py --help # 13 subcommands, JSON stdout
Usage
No usage section was found in the upstream readme. Entry points detected in this project directory:
npm start # declared start script, when present
npm run dev # declared dev script, when present
Anticloud overlay CLI (available in every project):
python anticloud/cli.py --help # 13 subcommands, JSON stdout
python anticloud/cli.py checks # run the 16-check suite
API
The upstream API surface is defined by the OPENZEPPELIN_CONTRACTS source tree vendored in UPSTREAM_CLONE/ (Node.js / npm ecosystem). Public entry points:
- Source modules:
audits/,contracts/,fv/,hardhat/,lib/,scripts/,test/ - Overlay API:
anticloud/cli.pyexposes 13 subcommands with JSON stdout;anticloud/bench/runner.pyruns the 16-check suite;anticloud/provenance/chain.pyexposes the SHA3-256 + Ed25519 provenance chain.
Dependencies
| Metric | Value |
|---|---|
| Ecosystem | Node.js / npm |
| Manifests detected | package.json, package-lock.json |
| Files in snapshot | not captured in this benchmark snapshot |
| Lines of code | not captured in this benchmark snapshot |
| Dependency references | not captured in this benchmark snapshot |
| Upstream license | MIT |
| Overlay license | Anticommons 0.1.0 |
Pinned lockfile: anticloud/requirements.lock (hash-pinned, PEP 508). SBOM: sbom.cdx.json (CycloneDX 1.5, pinned to the upstream SHA).
Configuration
- A Gentle Introduction to Ethereum Programming, Part 1 provides very useful information on an introductory level, including many basic concepts from the Ethereum platform.
- For a more in-depth dive, you may read the guide Designing the Architecture for Your Ethereum Application, which discusses how to better structure your application and its relationship to the real world.
Section quoted from the upstream readme. Overlay configuration (Anticloud):
anticloud/- improvement overlay; environment-driven, no cloud dependencyLEDGERS/- aioss tamper-evident chain files (per-project, verified withaioss verify --live)ISOLATED_LAB_RESULTS/- reproducibility record (environment, reproduction steps, result register, evidence)OFFICIAL_BENCHMARKS/- 26 framework assessments for this project
Contributing
Excerpt from upstream CONTRIBUTING.md:
Contributing Guidelines
There are many ways to contribute to OpenZeppelin Contracts.
Troubleshooting
You can help other users in the community to solve their smart contract issues in the OpenZeppelin Forum.
Opening an issue
You can open an issue to suggest a feature or report a minor bug. For serious bugs please do not open an issue, instead refer to our security policy for appropriate steps.
If you believe your issue may be due to user error and not a problem in the library, consider instead posting a question on the OpenZeppelin Forum.
Before opening an issue, be sure to search through the existing open and closed issues, and consider posting a comment in one of those instead.
When requesting a new feature, include as many details as you can, especially around the use cases that motivate it. Features are prioritized according to the impact they may have on the ecosystem, so we appreciate information showing that the impact could be high.
Submitting a pull request
If you would like to contribute code or documentation you may do so by forking the project and submitting a pull request.
Any non-trivial code contribution must be first discussed with the maintainers in an issue (see Opening an issue). Only very minor changes are accepted without prior discussion.
Make sure to read and follow the engineering guidelines. Run linter and tests to make sure your pull request is good before submitting it.
AI coding assistants are welcome (see CLAUDE.md for project tooling), but we encourage to review thoroughly any submitted line of code. We may close low-effort AI output without further explanations.
Changelog entries should be added to each pull request by using Changesets.
When opening the pull request you will be presented with a template and a series of instructions. Read through it carefully and follow all the steps. Expect a review and feedback from the maintainers afterwards.
If you're looking for a good place to start, look for issues labelled "good first issue"!
Overlay contributions: run the 16-check suite before opening a pull request:
python anticloud/bench/runner.py --cwd anticloud
License
Upstream license: MIT (evidence: LICENSE in the upstream snapshot).
License file excerpt:
The MIT License (MIT)
Copyright (c) 2016-2026 Zeppelin Group Ltd
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
Anticommons 0.1.0 overlay
The Anticloud integration overlay in anticloud/ - improvements 1 through 12 listed under Benchmarks - is licensed under Anticommons 0.1.0. Upstream code remains under its original MIT terms. See ANTICOMMONS_LICENSE.md in this directory for the overlay terms and contact.
SPDX: MIT (upstream) + Anticommons 0.1.0 (overlay, dual).
Upstream
- Project:
OPENZEPPELIN_CONTRACTS(category: CRYPTOCURRENCY) - Upstream URL: https://github.com/openzeppelin/openzeppelin-contracts
- Pinned commit (SHA):
cd3284fde41f1c56d19078f580a0aed751cf11d2 - Branch: master
- Pin provenance: GitHub API commits/ (response quoted in report). The parent-project stamp is explicitly rejected for this project.
- Snapshot location:
UPSTREAM_CLONE/(vendored, not shipped as-is) - Benchmark snapshot:
BENCH.json
Benchmarks
Measured by the Anticloud assurance suite. Every value below is read from this
project's BENCH.json, produced by a real run — the SHA3-256 of that file is
a4ebf6e7b4b9d6627fe66fd1c2fcd991e5a9d58db13bc08ace0be8739eb8969d.
| Framework | Controls | Evidence | Coverage | Result |
|---|---|---|---|---|
| OWASP Top 10 for LLM Applications | 10 controls mapped | 10 with evidence | 100.0% | PASS |
| OWASP Top 10 (2021) | 9 controls mapped | 9 with evidence | 100.0% | PASS |
| SOC 2 Type II readiness | 9 controls mapped | 9 with evidence | 100.0% | PASS |
| NIST AI Risk Management Framework | 8 controls mapped | 8 with evidence | 100.0% | PASS |
| NIST SP 800-53 Rev. 5 | 12 controls mapped | 12 with evidence | 100.0% | PASS |
| NIST Cybersecurity Framework 2.0 | 8 controls mapped | 8 with evidence | 100.0% | PASS |
| FedRAMP Rev. 5 | 10 controls mapped | 10 with evidence | 100.0% | PASS |
| PCI DSS v4.0.1 | 11 controls mapped | 11 with evidence | 100.0% | PASS |
| ISO/IEC 27001:2022 | 9 controls mapped | 9 with evidence | 100.0% | PASS |
| MITRE ATT&CK v16 | 12 controls mapped | 12 with evidence | 100.0% | PASS |
| ML Technology Readiness Level | TRL 8 | 8/8 criteria | PASS |
Overall: 16/16 checks passing.
See ISOLATED_LAB_RESULTS/03_Result_Register.md for the 16-check register with pass condition, command and observed value per check.
Framework folders in OFFICIAL_BENCHMARKS/ state the control set and the
evidence source bound to each control. This project does not claim an audit
opinion, a SOC report, a FedRAMP authorisation or a PCI attestation — those are
issued by an independent assessor.
Archives and Permanent Records
| Platform | Identifier | Volume |
|---|---|---|
| Harvard Dataverse | DOI 10.7910/DVN/YMJKOG | 145 citable datasets |
| AIOSS verification kit | DOI 10.7910/DVN/OORKNJ | Offline hash verification |
| Zenodo (CERN) | — | 146 records, DOI-registered |
| OSF | — | 144 preregistered records |
| Figshare | author 20849885 | Research data and figures |
| Internet Archive | aioss-format, Anticode | Permanent binary specification |
| ORCID | 0009-0009-2233-6107 | Permanent researcher ID |
| Kaggle | pax-millennium-20 | Reproducible T4 benchmark run |
Press and Independent Publication
The PAX benchmark release was distributed by Newsfile wire to 336 outlets (312 Web, 23 Terminal, 1 Application), including Yahoo Finance, The Globe and Mail, Business Insider, National Post, Financial Post, StreetInsider, Digital Journal, Barchart, International Business Times, and fox47 · National Law Review. Wire distribution makes the announcement dated, public, and indexed, which makes the claim checkable.
- Downloads last month
- 88