fritzkit@0.1.0
CAUTION· install onlyPublisher claims: "Enables agents to turn a JSON part specification into first-class Fritzing parts, with validation, rendering, export, and installation across breadboard, schematic, PCB, and icon views." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso githubusercontent.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 73/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Text pushed off-screen by whitespace; README links to an external installer; Destructive file system command detected. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
* carrying the human message, never as an exception that would kill the server.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.| a WARNING about gaps after removing pins is expected and harmless; never renumber `pinIds` to "fix" it |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.https://files.seeedstudio.com/wiki/XIAO-KiCad-Library/New_XIAO_Series_Footprints.zipFix: Pin versions and sources; vendor anything fetched at install time.| step | CLI (`npx fritzkit ...` or `fritzkit ...`) | MCP tool (server `fritzkit`) |Fix: Pin versions and sources; vendor anything fetched at install time./** Convert a parsed footprint into a part.json fragment (PartSpecInput). */Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Folders first; only ids whose folder is really gone leave the bin, so a failed rmFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* Only part.json and assets/ feed the compiler, so build output never changes a moduleId.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… Parts. You do the research and vision work with your own tools; fritzkit (CLI `npx fritzkit` or the `fritzkit` MCP server) is offline and deterministic. --- # fritzkit: bu…Fix: Pin versions and sources; vendor anything fetched at install time.{ description: "Return the part.json JSON Schema.", inputSchema: { workspace: ws } },Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* Validate a part.json body for PUT. Returns the raw object to write (with connectorFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
7 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim pmaxhogan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- README links to an external installer≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.