pixijs-scene-dom-container 100/100

Is pixijs-scene-dom-container safe to install?

SaferSkills independently audited pixijs-scene-dom-container (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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/pixijs/skills/pixijs-scene-dom-container/SKILL.md · 1 file

plugins/pixijs/skills/pixijs-scene-dom-container/SKILL.md1.2 KB · Markdown

name: pixijs-scene-dom-container

description: "Use for PixiJS v8 DOMContainer overlays: HTML elements attached to scene nodes, pixi.js/dom import, element/anchor options, CSS transforms, visibility and resize sync."

license: MIT

Use this when real DOM elements must visually follow PixiJS scene nodes above the canvas.

Rules

Import pixi.js/dom before using DOMContainer.
Append app.domContainerRoot next to app.canvas so DOM overlays can be placed correctly.
Use DOMContainer for live HTML interaction; use HTMLSource only for texture snapshots.
Keep CSS and Pixi transforms in sync through the scene graph; test resize and visibility changes.
Do not expect DOM elements to participate in WebGL batching, filters, masks, or canvas extraction.

Deep Reads

Full DOMContainer setup and limitations: references/details.md
Application root: pixijs-application
HTML snapshots as textures: pixijs-html-source

Common Fixes

Element not visible: check pixi.js/dom import and app.domContainerRoot placement.
Pointer layering issue: inspect CSS pointer-events and z-order.
Need filtered DOM: render it as a texture snapshot instead, accepting experimental limits.

pixijs-scene-dom-container— agent skill

Is pixijs-scene-dom-container safe to install?

Rules

Deep Reads

Common Fixes

Audit the pieces. Scan the whole. Decide.