Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
AgentDossier · AI Agent Registry Find agents you can actually trust - public or inside your enterprise.
Technology & Software Engineering Top 100 / #–ARD = Agentic Resource Discovery · A2A = Agent2Agent · MCP = Model Context Protocol
Hugging Face Space · agent · hosted

CUGA Agent

Configurable Generalist Agent, leader in AppWorld Benchmark Publisher: ibm-research.

Vendor page ↗+ CompareExport JSON
Trust profileas of 2026-10-26
Publisherlikely · Repository ownership or inferred publisher domain — repository or Hub account ownershiplikely
Complianceno evidence about this agent · 15 vendor-level records (inherited)T5
SecurityNo CVE linked to this agent in the CVE registry — none linked in the products checked, not a findingnone
ProtocolsModel Context Protocol (MCP) not checked — not probed: URL is on a code host, which never carries a publisher's well-known filesAgent2Agent (A2A) not checked — not probed: URL is on a code host, which never carries a publisher's well-known filesAgentic Resource Discovery (ARD) not checked — not probed: URL is on a code host, which never carries a publisher's well-known files0 / 3
TracesNone found — nobody has published what this agent does under attacknone
Issues found0 regulator actions · 0 incidents · 0 withdrawn certificates · CVEs: see Securitylinks only

Publisher unconfirmed: the evidence below is shown but not counted in the governance score, because nothing yet ties this listing to ibm-research beyond repository or Hub account ownership. A vendor-domain page, marketplace listing, ARD manifest or A2A card would confirm it.

Evidence available — not a safety certification. Suitability depends on your task, deployment and permissions. Rows marked vendor-level describe ibm-research, not this agent specifically.

Traces — under attack, in defence, in incidents

none public · what a trace is

No public trace found. Nobody has published what CUGA Agent does when its inputs carry instructions it should not follow, when a tool asks for credentials, or when a task invites a destructive command. Defenders can't learn from what they can't see: run it in a sandbox before the pilot and keep the transcript, or ask the vendor to publish one.

● third-party or vendor report · ◎ this registry's own probe transcript · ⚠ data left the environment. A trace describes one version on one date; it is evidence of behaviour, never a certification. Rows marked unreviewed have not yet been checked against their source by the maintainer.

CVEs — on the official record

none linked · the registry

No CVE in the registry names this agent or its listed product. That reads "none linked in the products checked", never as a finding: a product that is not on the registry's list, or a record that names it differently, is not seen. The vendor's own advisories remain the source of truth.

Compliance evidence

Jurisdiction: US + EU · 16 frameworks shown
–
ISO 42001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor

"Unknown" means nothing was found in the sources checked — registries, marketplaces and the vendor's own pages. It is not a finding of non-compliance; ask the vendor.

About the vendor — inherited, not agent-specific

15 records matched at organisation level
✔
FedRAMP · FedRAMP High
T1 Registry-matched · vendor-level
FedRAMP Authorized
Scope: entity · covers this resource: inherited · FedRAMP Marketplace · 2026-10-26
re-check 2026-11-02
○
CSA STAR
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
DORA
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
FedRAMP
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
GDPR
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
GDPR · DPF active
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
HIPAA
T4 Vendor-claimed · vendor-level
BAA available
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
HITRUST
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
IRAP
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
ISO 27001 · ISO 27001
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
ISO 27001 · ISO 27017
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
ISO 27001 · ISO 27018
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
ISO 27701 · ISO 27701
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
PCI DSS
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02
○
SOC 2
T4 Vendor-claimed · vendor-level
Vendor-claimed
Scope: entity · vendor page · 2026-10-26
re-check 2026-11-02

A vendor-level registry entry proves the organisation was assessed; whether this agent is inside that scope is a question for the vendor. These rows do not count toward the agent's evidence tier.

✔ found · ○ claimed · – not found · ⚠ expired, stale or revoked. Every row links to its source.Dispute or correct this dossier

GDPR, assembled from checks

GDPR● 0 found in registries or documents○ 3 vendor-claimed⚠ 0 issues linkedas of 2026-10-26
○ ClaimedVendor-claimed (vendor page, 2026-10-26).
○ ClaimedDPF active: Vendor-claimed (vendor page, 2026-10-26). Proves a transfer mechanism for EU-to-US transfers only.
○ ClaimedISO 27701: Vendor-claimed (vendor page, 2026-10-26). Privacy management system; covers the organization, not this agent specifically.
– Not foundNo Article 42 GDPR seal. "GDPR certified" is never shown without one.
☐ You checkYour lawful basis, DPIA, and whether this agent is inside the certificate scope.

News and chatter

last 90 days · linked with confidence ≥ 0.85

Nothing linked from Hacker News, GDELT, GitHub releases or the vendor's feed in the last 90 days.

Headline, link and a summary attributed to the outlet. News never changes trust or domain scores.

Technology & Software Engineering score

45
technology profile · sar-score-2.0 · unranked
Adoption / usage18 / 30
Trust & security15 / 25
Project / product health8 / 20
Ecosystem / interoperability0 / 15
Domain expertise / fit34 / 100
Governance / compliance evidence0 / 100
Docs / transparency7 / 10

Raw component / maximum, then weighted by the technology profile (adoption 30, trust 20, project 20, ecosystem 15, domain 10, governance 0, docs 5). Trust and governance are computed from the evidence on this page (vendor-level rows at half credit); the other components come from the curated workbook, whose order is the rank. Unknown components count as 0 and are never imputed.

Before you deploy

Derived from the evidence ledger. This agent is not yet in the reference set, so deployment questions (credentials, approval, data handling) are not answered here — ask the vendor.

Evidence supporting this use (15)
FedRAMP High — registry-matched, vendor-level source
CSA STAR — vendor-claimed, vendor-level source
DORA — vendor-claimed, vendor-level source
FedRAMP — vendor-claimed, vendor-level source
GDPR — vendor-claimed, vendor-level source
GDPR DPF active — vendor-claimed, vendor-level source
HIPAA — vendor-claimed, vendor-level source
HITRUST — vendor-claimed, vendor-level source
IRAP — vendor-claimed, vendor-level source
ISO 27001 — vendor-claimed, vendor-level source
ISO 27001 ISO 27017 — vendor-claimed, vendor-level source
ISO 27001 ISO 27018 — vendor-claimed, vendor-level source
ISO 27701 — vendor-claimed, vendor-level source
PCI DSS — vendor-claimed, vendor-level source
SOC 2 — vendor-claimed, vendor-level source
Unknowns to check (6)
Your lawful basis and DPIA for PHI and personal data the agent will touch
That the SOC 2 report period covers the components you will use; request the report under NDA
That the HIPAA BAA is offered for this product tier and region
Whether the ISO 27001 certificate scope names this service, or only the platform
Current FedRAMP status with the agency, if government use is intended
Whether the CSA STAR entry covers this product; Level 1 is a self-assessment, Level 2 a third-party attestation
Suggested restrictions for a pilot (1)
No public trace of this agent under adversarial input was found. Run it in a sandbox against your own prompt-injection and tool-abuse scenarios before the pilot, and keep the transcript; the enterprise edition records one.

Rules: config/deploy_rules.json. Advice for a bounded pilot, not a verdict.

Provenance

Hugging FaceHub signals
FedRAMP Marketplacecompliance evidence
vendor pageclaims
NVDsecurity (CVE keyword search)
Hacker News, GDELT, vendor feedsnews and chatter
First seen2026-10-26
Recordres_fe0bceed6588bf46
Open the full record (JSON) →