Skip to main content
VLSI Korea

SEMICONDUCTOR INTELLIGENCE

See the connections.
Follow the evidence.

Explore companies, chips, technologies and facilities through documented claims. Select a connection to see its source, scope and dates.

Coverage & methods

Search canonical names and aliases. Results reflect the current entity collection.

Browse the entity collection
Reset

Unknown validity is excluded when a validity date is selected. Knowledge time records what VLSI had observed; it is separate from the relationship’s valid time.

4 entities and 3 documented connections shown.

CURRENT STARTING ENTITY

OpenROAD Flow Scripts

open source project · 4/40 entities · 3/60 connections · 1 relationship step

Canonical entity →

Knowledge snapshot: · Relationship dates may differ

Relationship map

Arrows follow the claim’s direction. Tab to a node or connection; press Enter to inspect it.

100%
STARTING ENTITY1 RELATIONSHIP STEPUses tool · SUPPORTEDUses tool · SUPPORTEDUses tool · SUPPORTEDYosys · eda toolEDA TOOLYosysKLayout · eda toolEDA TOOLKLayoutOpenROAD · eda toolEDA TOOLOpenROADOpenROAD Flow Scripts · open source projectOPEN SOURCE PROJECTOpenROAD Flow Scripts
CompaniesChips & productsTechnologiesFacilities & places

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.

SUPPORTED records a source-backed assertion. VERIFIED requires an identified human review. This map does not measure supplier concentration or prove that an unrecorded relationship is absent.

ACCESSIBLE RELATIONSHIP VIEW

Every connection, with its evidence.

3 recorded claims
Claims in the current graph. Each arrow runs from subject to object.
SubjectRelationshipObjectStatus & datesEvidence
OpenROAD Flow ScriptsKLayoutSUPPORTEDValidity dates not established
Why are these connected? · 1 source(s)

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.

Claim history →
OpenROAD Flow ScriptsOpenROADSUPPORTEDValidity dates not established
Why are these connected? · 1 source(s)

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.

Claim history →
OpenROAD Flow ScriptsYosysSUPPORTEDValidity dates not established
Why are these connected? · 1 source(s)

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.

Claim history →
Entities in this view (4)

EVIDENCE PATHFINDER

How are two entities connected?

Up to 2 documented steps

Find paths from OpenROAD Flow Scripts. Each step retains its own claim and evidence; a path does not establish a new supply relationship.