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.
Technology & Software Engineering Top 100 / #–ARD = Agentic Resource Discovery · A2A = Agent2Agent · MCP = Model Context Protocol
Open-source project · Other · self-hosted

superplane

Open source factory for one-shot engineering Publisher: superplanehq.

Trust profileas of 2026-10-26
Publisherlikely · Repository ownership or inferred publisher domain — repository or Hub account ownershiplikely
Complianceno evidence about this agent · 1 vendor-level record (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) probed, not foundAgent2Agent (A2A) probed, not foundAgentic Resource Discovery (ARD) probed, not found0 / 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 superplanehq 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 superplanehq, 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 superplane 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

4 frameworks shown
–
ISO 27001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
ISO 42001
T5 Unknown
Nothing found in the sources checked.
Scope: — · registries, marketplaces, vendor pages
ask the vendor
–
CSA STAR
T5 Unknown
Nothing found in the sources checked.
Scope: — · CSA STAR Registry
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

1 record matched at organisation level
○
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○ 0 vendor-claimed⚠ 0 issues linkedas of 2026-10-26
– 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
2026-10-24
SuperPlane v1.0.0-rc7
GitHub releases · Source commit: eca2e98cdba7178dad4889e5e0f573fdd03aed6a SuperPlane image digest: `sha256:b5ff8cba84b22f8105933652228f9a01dd41a88e18dd38d49c81b838b8f2a7da` SuperPlane chart digest: `sha256:fafcdf49e965dd482c8ee34cf8a9eb50de23aa249a9cb9f310
Product update
2026-10-24
superplane: Fleet Manager v0.1.6
GitHub releases · Source commit: 155f5242eafeca886871a809e2f6823d490b53f6 Fleet Manager image digest: `sha256:80ec8697de61c7a2bf7040dc16cf0538af9cb64a41595bbdef469983a4b2b4e4` Fleet Manager chart digest: `sha256:3f7584db9f0c330b6594ad6c0e04e322f17f8257a841
Product update

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

Technology & Software Engineering score

70
technology profile · sar-score-2.0 · unranked
Adoption / usage23 / 30
Trust & security16 / 25
Project / product health20 / 20
Ecosystem / interoperability3 / 15
Domain expertise / fit81 / 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 (1)
SOC 2 — vendor-claimed, vendor-level source
Unknowns to check (3)
That the SOC 2 report period covers the components you will use; request the report under NDA
Ask the vendor for ISO 27001, ISO 42001, CSA STAR evidence; none was found in the sources checked
Whether the agent exposes MCP or A2A endpoints; none were observed
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

GitHubrepository signals, license
vendor pageclaims
NVDsecurity (CVE keyword search)
Hacker News, GDELT, vendor feedsnews and chatter
First seen2026-10-26
Recordres_47130c69f8a9e878
Open the full record (JSON) →