yfiles-nodestyle-advanced — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited yfiles-nodestyle-advanced (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Implement viewport culling, custom rendering bounds, and group node styles.
Always query the yFiles MCP for current API:
yfiles:yfiles_get_symbol_details(name="NodeStyleBase")
yfiles:yfiles_list_members(name="NodeStyleBase")
yfiles:yfiles_search_documentation(query="group node style")
yfiles:yfiles_get_symbol_details(name="INode")export class AdvancedNodeStyle extends NodeStyleBase {
protected isVisible(
context: ICanvasContext,
rectangle: Rect,
node: INode
): boolean {
// Only render if node intersects viewport
return node.layout.toRect().intersects(rectangle)
}
protected getBounds(context: ICanvasContext, node: INode): Rect {
// Return actual rendering bounds (including badges, shadows, etc.)
return node.layout.toRect().getEnlarged(10)
}
}node.layout (badges, decorators)Note: When implementing yFiles interfaces, always use BaseClass() wrapper instead of TypeScript implements. The @yfiles/eslint-plugin rule @yfiles/fix-implements-using-baseclass enforces this pattern.
isVisible() strategies, getBounds() patterns, group node API, performance considerations/yfiles-nodestyle-basic — Start here for rendering fundamentals/yfiles-nodestyle-configure — Data-driven configuration/yfiles-nodestyle-interaction — Hit testing and edge cropping~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.