5 findingsStatic scanned
Starts an AI-edited video project in any directory and hands it to Claude Code or opencode.
13k installs/moMIT
Spine Rigc
firejune · Template
Rig compiler for Spine 2D animation, built so AI agents can author rigs and check their own work, and shipped as an agent skill. From loose part PNGs, a rig spec and a motion spec it writes a skeleton file and atlas that load in a Spine runtime and import into the Spine editor, but only when named assertions pass; otherwise it names the failed rule and writes nothing. Other commands render frames, build an HTML preview and make a ballot page. It runs with Bun, and playing the output in a product with a Spine runtime falls under Spine's licence terms.
Written by ooruby from the README of spine-rigc 2.32.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Lets an agent draft Spine rigs and animation that are checked against named assertions before anything is written.
What you could do with it
- Build a skeleton file and atlas from part PNGs, a rig spec and a motion spec, or get the failed rule named.
- Render every animation of a compiled rig as PNG frames plus a labelled contact sheet.
- Put two to four compiled rigs on one ballot page so a person can pick the winner.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (tools/editor_roundtrip.ts:62)
- synchronous shell execution (tools/editor_roundtrip.ts:622)
- node child_process (bin/rigc.cjs:33)
- synchronous shell execution (bin/rigc.cjs:57)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
AI-authored Spine 2D rigging and animation, verified before it is written. rigc compiles a rig spec into Spine 4.3 skeleton data, gates it with named assertions held to a spine-core round trip's verdicts, and emits nothing that fails. Output imports into
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.32.2, the file with digest sha512-/6cJrT1KxjrBxKXZMNiPc0zfxN4gTr072+SP23WD6sSWq3f4uaerD3Z0xX/U2/mufeVo4sTR2WAP6IT9CdBrJQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y spine-rigc@2.32.2Pinned to 2.32.2, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- spine-rigc
- Version read
- 2.32.2
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/firejune/rigc
- Commit
- 04c94fc4efe3
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/spine-rigc)About this listing
- Kind
- Template
- Category
- Content
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
Similar templates
All templatesVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.