Semiconductor graph

OpenROAD Flow Scripts

10 entities and 14 documented connections shown.

AI / computeNVIDIA FoundriesTSMC AI / computeAMD MemorySK hynix Open siliconOpenROAD Flow Tiny TapeoutTT 8 Tiny TapeoutTT 9 Tiny TapeoutTT IHP 26a Tiny TapeoutTT SKY 26a

Filters & dates 2 steps

Relationship stepsRelationshipEntity typeRelationship valid onKnown by UTC dateClear filters

Validity and knowledge time are separate. Unknown validity is excluded from dated queries.

2,343 covered entities2,781 recorded claims2,248 indexed resourcesCoverage & gaps →

Includes catalog identities and shuttle listings.

CompanyChip / productTechnologyPlace / facility

Select a connection for its evidence

Relationships & evidence (14)

Every displayed connection is a scoped claim. Arrows follow subject to object.
Subject	Object	Status	Evidence
OpenROAD Flow Scripts	KLayout	SUPPORTEDValidity dates not established	Why are these connected? KLayout is documented for the finishing stage. This is not a verified signoff result. OpenROAD Flow Scripts README The OpenROAD Project · Tier A · Primary source · supports The ORFS flow diagram assigns GDSII generation and DRC/LVS checks to KLayout. Location: Pinned README.md line 43: GDSII generation and layout checks Published Not stated Retrieved 2026-10-13 Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity. Full claim history →
SymbiYosys	Yosys	SUPPORTEDValidity dates not established	Why are these connected? SymbiYosys describes itself as a front-end for Yosys-based formal verification flows; solver and frontend selection affect applicability. symbiyosys pinned upstream documentation Official symbiyosys repository · Tier A · Primary source · supports SymbiYosys describes itself as a front-end for Yosys-based formal verification flows; solver and frontend selection affect applicability. Location: README / Introduction Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenLane 2	Yosys	SUPPORTEDValidity dates not established	Why are these connected? OpenLane describes Yosys among its infrastructure components. openlane2 pinned upstream documentation Official openlane2 repository · Tier A · Primary source · supports OpenLane describes Yosys among its infrastructure components. Location: Readme / ASIC infrastructure components Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
Yosys	SymbiYosys	SUPPORTEDValidity dates not established	Why are these connected? The Yosys README links SBY as its formal verification front-end; installed solvers and supported syntax remain separate requirements. yosys pinned upstream documentation Official yosys repository · Tier A · Primary source · supports The Yosys README links SBY as its formal verification front-end; installed solvers and supported syntax remain separate requirements. Location: README / Web Site and Other Resources Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenROAD Flow Scripts	Yosys	SUPPORTEDValidity dates not established	Why are these connected? The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow. openroad pinned upstream documentation Official openroad repository · Tier A · Primary source · supports The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow. Location: README / RTL-GDSII Using OpenROAD-flow-scripts Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
Yosys	Verilator	SUPPORTEDValidity dates not established	Why are these connected? The README recommends a separate Verilator lint check because the read_verilog command does not perform syntax checking. yosys pinned upstream documentation Official yosys repository · Tier A · Primary source · supports The README recommends a separate Verilator lint check because the read_verilog command does not perform syntax checking. Location: README / Additional information Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenROAD Flow Scripts	SKY130 Open PDK	SUPPORTEDValidity dates not established	Why are these connected? The README names SKY130 among open PDKs supported in OpenROAD-flow-scripts; a selected platform and library configuration is required. openroad pinned upstream documentation Official openroad repository · Tier A · Primary source · supports The README names SKY130 among open PDKs supported in OpenROAD-flow-scripts; a selected platform and library configuration is required. Location: README / PDK Support Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
Ibex	Yosys	SUPPORTEDValidity dates not established	Why are these connected? Ibex README describes Yosys area evaluation using its basic synthesis flow and latch-based register file. No area figures are republished. ibex pinned upstream documentation Official ibex repository · Tier A · Primary source · supports Ibex README describes Yosys area evaluation using its basic synthesis flow and latch-based register file. No area figures are republished. Location: README / Configuration / Yosys synthesis notes Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenROAD Flow Scripts	OpenROAD	SUPPORTEDValidity dates not established	Why are these connected? ORFS documents OpenROAD use. Its README restricts guarantees to the latest matching OpenROAD/ORFS and warns that third-party versions are not guaranteed. OpenROAD Flow Scripts README The OpenROAD Project · Tier A · Primary source · supports The ORFS installation documentation identifies OpenROAD among its provided flow applications. Location: Pinned README.md line 89: Physical implementation flow Published Not stated Retrieved 2026-10-13 Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity. Full claim history →
OSS CAD Suite	Yosys	SUPPORTEDValidity dates not established	Why are these connected? Listed distribution component at the pinned README revision; availability depends on the upstream release and supported platform. Component license is not replaced by the distribution license. OSS CAD Suite README YosysHQ · Tier A · Primary source · supports The OSS CAD Suite README lists Yosys among its distribution components. Location: Pinned README.md line 33: RTL synthesis Published Not stated Retrieved 2026-10-13 Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity. Full claim history →
OpenLane 2	OpenROAD	SUPPORTEDValidity dates not established	Why are these connected? OpenLane describes OpenROAD among its infrastructure components. openlane2 pinned upstream documentation Official openlane2 repository · Tier A · Primary source · supports OpenLane describes OpenROAD among its infrastructure components. Location: Readme / ASIC infrastructure components Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenROAD Flow Scripts	KLayout	SUPPORTEDValidity dates not established	Why are these connected? The described ORFS finishing stage uses KLayout for GDSII output and DRC/LVS checks. openroad pinned upstream documentation Official openroad repository · Tier A · Primary source · supports The described ORFS finishing stage uses KLayout for GDSII output and DRC/LVS checks. Location: README / ORFS Finishing Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenLane 2	KLayout	SUPPORTEDValidity dates not established	Why are these connected? OpenLane describes KLayout among its infrastructure components. openlane2 pinned upstream documentation Official openlane2 repository · Tier A · Primary source · supports OpenLane describes KLayout among its infrastructure components. Location: Readme / ASIC infrastructure components Published Not stated Retrieved 2026-10-13 Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms. Full claim history →
OpenROAD Flow Scripts	Yosys	SUPPORTEDValidity dates not established	Why are these connected? Yosys is documented for the synthesis stage of OpenROAD Flow Scripts at this source revision. OpenROAD Flow Scripts README The OpenROAD Project · Tier A · Primary source · supports The ORFS flow diagram assigns logic synthesis to Yosys. Location: Pinned README.md line 19: RTL synthesis Published Not stated Retrieved 2026-10-13 Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity. Full claim history →

Find an evidence path

Find a documented path

From OpenROAD Flow Scripts · up to two relationship steps.

A path retains its original claims. Shared technology does not establish a supply contract.

10 nodes · 14 claims2026-10-14 · 10:08 UTC

Scope

Relationships may describe different dates. A path does not establish simultaneous activity. Bounded source-backed collection. Missing or filtered connections do not establish absence. Supported does not mean independently verified.

Search, filters and the expandable relationship evidence table work without JavaScript. The map controls and path results require JavaScript; path submissions open the structured API response.

Connections

Find a documented path