Ontology
AOPO
Adverse Outcome Pathway Ontology
The AOPO provides classes and relationships for the semantic representation of the Adverse Outcome Pathway framework.
Source & access
- homepage github.com HTTP 200
- repository github.com HTTP 200
- download github.com HTTP 200
Automated evaluation
F Findable FAIR4/12
- Persistent identifier (F1)no PURL / w3id / DOI for the artefact0
- Indexed in services (F4)1: Bioregistry+1
- Citable reference (F2)doi:10.1089/aivt.2017.0017+3
A Accessible FAIR12/12
- Homepage reachableHTTP 200+3
- Artefact retrievable over HTTP(S) (A1)download HTTP 200+6
- Metadata persists in a registry (A2)Bioregistry+3
I Interoperable FAIR8/12
- Formal machine-readable format (I1)OWL+5
- Semantic-web IRIs (I2)OWL+3
- References other vocabularies (I3)no imported vocabularies found0
R Reusable FAIR7/12
- Clear license (R1.1)Apache-2.0+5
- Release provenance (R1.2)v1.0.0 (latest GitHub release); not declared inside the artefact+2
- Community standards (R1.3)no independent compliance report (not on the OBO Dashboard)0
Q Ontology consistency & quality0/20
- Logical consistencynever checked by a reasoner0
- OWL 2 DL profileprofile not checked0
- Upper-ontology alignmentno BFO/COB/DOLCE import found0
- Standard relations (RO)does not import the Relation Ontology0
- ROBOT report: no errorsno ROBOT report available0
- ROBOT report: warning densityno ROBOT report available0
- Pitfall scan: no critical pitfallsno pitfall scan or ROBOT report yet0
M Maintenance0/16
- Recency2024-04-01 → 30.8 months (older / unknown)0
- Release cadence (12 months)0 releases (GitHub releases)0
U Community adoption2/16
- Documented adopting projects0 projects0
- Reused by other ontologies00
- Community signalmax(stars 13 → 1, citations 73 → 2)+2
P Penalties (inactivity & inconsistency)-6
- Time since last activity2.6 years → 4 × max(0, 2.6 − 1)-6
- Inactive statusnot archived, legacy or inactive0
- Consistencynot yet checked by a reasoner0
FAIR subtotal 31/48 · earned 33/100 − 6 inactivity = 27/100 → grade E
Community adoption 0
No adopting projects documented yet.
Know a project that uses AOPO? Suggest it.
History & changes 1 run
History starts with the first archived run; changes appear after the next evaluation.
| Run | Score | FAIR | Version evaluated | Terms | Snapshot |
|---|---|---|---|---|---|
| 26 Oct 2026, 03:31 UTC | 27 E | 31 | v1.0.0 | — | JSON |
Provenance
Every fact on this page was fetched automatically. Each row shows where it came from and when. If a source fails, the last good value is kept and marked “carried forward”.
| Fact | Source | Retrieved |
|---|---|---|
| Homepage link check (HTTP 200) | github.com | 26 Oct 2026, 02:38 UTC |
| Repository link check (HTTP 200) | github.com | 26 Oct 2026, 02:38 UTC |
| Download link check (HTTP 200) | github.com | 26 Oct 2026, 02:38 UTC |
| Artefact header | raw.githubusercontent.com | 26 Oct 2026, 02:38 UTC |
| Git refs (commit 626176c, latest tag v1.0.0) | github.com | 26 Oct 2026, 02:38 UTC |
| GitHub repository statistics | api.github.com | 26 Oct 2026, 02:38 UTC |
| Bioregistry mappings, dependencies & reuse | bioregistry.io | 26 Oct 2026, 02:38 UTC |
| Crossref citations (doi:10.1089/aivt.2017.0017) | api.crossref.org | 26 Oct 2026, 02:38 UTC |
Run 2026-10-26T02-37-38Z · evaluator v2.0.0 · rubric v3.4 · entry.json · run snapshot
How to cite
- Creating a Structured Adverse Outcome Pathway Knowledgebase via Ontology-Based Annotations (2017) · doi:10.1089/aivt.2017.0017 · 73 citations