OpenData
OpenData
| Field | Value |
|---|---|
| Distribution | BSS — OpenSOF |
| Product | OpenSOF |
| Release | 0.15.1 |
| Deployment | opensof.bss.dev |
| Source | /srv/bss/releases/OpenSOF-v0.15.0-20app |
| Evidence | Catalog intent plus component-scoped static evidence |
| Source fingerprint | cda583b42f2a0d296b268ab5b174932a378c8be6fb52ffa1af14af896e990f6e |
| Status | Generated baseline — human review required |
Verification boundary: This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.
Purpose
The ingestion, normalization, storage and data-access capability for structured, semi-structured, streaming and file-based information.
Operational value
Creates a reusable data foundation for operational applications, analytics and evidence preservation without forcing every module to build its own data plumbing.
Differentiators
Data handling is tied to semantic types, provenance and real-time operational use instead of being isolated in a heavyweight enterprise data program.
Platform connections
- OpenKnowledge
- OpenAnalytics
- OpenDAA
- OpenFiles
Release detection
| Status | Score | Evidence items |
|---|---|---|
| detected | 105 | 12 |
| Evidence type | Source | Match |
|---|---|---|
| path | OPENDAA-OPENDATA.md |
opendata |
| path | .opennetworks-backup-20260827T210646Z/ontology/opendaa-opendata.ttl |
opendata |
| path | data/opendata.json |
opendata |
| path | lib/opendata.js |
opendata |
| path | ontology/opendaa-opendata.ttl |
opendata |
| content | API.md |
opendata |
| content | CHANGELOG.md |
opendata |
| content | MERGE-v0.13.1.md |
opendata |
| content | OPENCYBERSEC.md |
opendata |
| content | OPENDAA-OPENANALYTICS.md |
opendata |
| path | open-daa/open-data/app.js |
open-data |
| path | open-daa/open-data/index.html |
open-data |
Candidate REST/API interfaces
No component-specific REST route was associated by the scanner.
Candidate real-time interfaces
No component-specific WebSocket endpoint was associated by the scanner.
Configuration candidates
| Variable | Default | Evidence |
|---|---|---|
BASE |
http://127.0.0.1:3000 | DEPLOY-GODADDY.md, OPENCYBERSEC-QUICKSTART.md, OPENCYBERSEC.md, UPGRADE-v0.14.0.md |
DATA_DIR |
path.join(ROOT | OPENCYBERSEC-QUICKSTART.md, OPENCYBERSEC.md, RELEASE-MANIFEST-v0.14.0.json, UPGRADE-v0.14.0.md |
OPENCYBERSEC_AGENT_TOKEN |
[REDACTED] | OPENCYBERSEC-QUICKSTART.md, OPENCYBERSEC.md, server.js, examples/opencybersec/ingest-examples.sh |
OPENCYBERSEC_OPERATOR_TOKEN |
[REDACTED] | OPENCYBERSEC-QUICKSTART.md, OPENCYBERSEC.md, server.js, examples/opencybersec/ingest-examples.sh |
RUN_ID |
— | OPENCYBERSEC.md |
Service candidates
No component-specific service definition was associated by the scanner.
External dependencies/endpoints
| Host | URL | Source |
|---|---|---|
| loammhpng4.c36.airoapp.ai | https://loammhpng4.c36.airoapp.ai/ |
API.md |
| loammhpng4.c36.airoapp.ai | https://loammhpng4.c36.airoapp.ai/ |
CHANGELOG.md |
| opensof.local | https://opensof.local/ontology |
.opennetworks-backup-20260827T210646Z/ontology/opendaa-opendata.ttl |
| opensof.local | https://opensof.local/ontology |
ontology/opendaa-opendata.ttl |
| opensof.local | https://opensof.local/ontology/opendaa-opendata |
.opennetworks-backup-20260827T210646Z/ontology/opendaa-opendata.ttl |
| opensof.local | https://opensof.local/ontology/opendaa-opendata |
ontology/opendaa-opendata.ttl |
| opensof.local | https://opensof.local/resource/ |
.opennetworks-backup-20260827T210646Z/ontology/opendaa-opendata.ttl |
| opensof.local | https://opensof.local/resource/ |
ontology/opendaa-opendata.ttl |
Verification checklist
- Confirm the component is included and enabled in this edition/release.
- Record its authoritative service, process/container, port, base URL and health endpoint.
- Exercise its primary operator workflow and capture expected versus actual results.
- Verify authentication, authorization, audit, error behavior and data handling policy.
- Verify OpenBus/OpenKnowledge relationships and time/provenance metadata where applicable.
- Document known limitations and the release in which they are corrected.
Maintainer Notes
Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.