core@0.36.0
CAUTION· install onlyPublisher claims: "User files for a SaaS, under one person's authority: list, share with an expiry, revoke." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 2 of 2 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 0.35.2
vet-skills diff core 0.35.2 0.36.0This version reaches for something 0.35.2 did not: 1 new host (filelayer.invalid) · 4 new credential variables (DATABASE_URL, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, S3_SESSION_TOKEN). Compared from the two recorded runs, not from source.
- New hosts
- filelayer.invalid
- New credential variables
- DATABASE_URL, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, S3_SESSION_TOKEN
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-20 and scored it 74/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: Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration; HTML comment carrying imperative instructions to the agent. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
* hot-reloaded or monkey-patched role table.Fix: Pin versions and sources; vendor anything fetched at install time.* hot-reloaded or monkey-patched role table.Fix: Pin versions and sources; vendor anything fetched at install time.* npx filelayer schema statusFix: Pin versions and sources; vendor anything fetched at install time.doccheck: skip reason="it connects a server to stdio and never returns, and it imports the MCP SDK, which is an optional peer this checker does not install"Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.* hot-reloaded or monkey-patched role table.Fix: Pin versions and sources; vendor anything fetched at install time.* npx filelayer doctorFix: Pin versions and sources; vendor anything fetched at install time.* npx filelayer doctorFix: Pin versions and sources; vendor anything fetched at install time.// file stricter than asked. A mutation removing that chmod survived theFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.pretend to. A convincing permission check layered on root access is worse thanFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.* log", as schema.sql puts it). A filter that excluded them would answer "noFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* npx filelayer schema statusFix: Pin versions and sources; vendor anything fetched at install time.* log", as schema.sql puts it). A filter that excluded them would answer "noFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// A soft-deleted org. Deleting one used to kill memberships and leave grantsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.const { id } = await fl.files.put(utf8('<script>alert(document.cookie)</script>'), {Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.-- survives the suite, and a guard no test can kill is a guard whoseFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// file stricter than asked. A mutation removing that chmod survived theFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.top of root access is worse than no check, because it reports that somethingFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…. All read authorization lives in `authz.ts`. There is no RLS policy in\n`schema.sql`, so a client that queries the tables directly is not filtered by\nanything and writes no audit event. Filelayer composes with database-level\nenforcement…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* npx would otherwise not install:Fix: Pin versions and sources; vendor anything fetched at install time.… and enforces -- the CLI cannot enforce anything. A permission check layered on root access is worse than no check: it reports that something was authorized when nothing w…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.convincing check on top of root access that the same header refuses. Reading asFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.* npx filelayer doctorFix: Pin versions and sources; vendor anything fetched at install time.' npx -y -p @filelayer/core -p pg -p @modelcontextprotocol/sdk -p zod filelayer-mcp',Fix: Pin versions and sources; vendor anything fetched at install time.!r.out.includes('AKIAIOSFODNN7EXAMPLE'),Fix: Never read or enumerate credential locations; accept a documented environment variable instead.const AK = 'AKIAFILELAYERTEST000';Fix: Never read or enumerate credential locations; accept a documented environment variable instead.'AKIAIOSFODNN7EXAMPLE</Message></Error>',Fix: Never read or enumerate credential locations; accept a documented environment variable instead.* npx would otherwise not install:Fix: Pin versions and sources; vendor anything fetched at install time.* npx would otherwise not install:Fix: Pin versions and sources; vendor anything fetched at install time.-- survives the suite, and a guard no test can kill is a guard whoseFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.' npx -y -p @filelayer/core -p pg -p @modelcontextprotocol/sdk -p zod filelayer-mcp',Fix: Pin versions and sources; vendor anything fetched at install time.* npx filelayer schema statusFix: Pin versions and sources; vendor anything fetched at install time.{ env: { ...process.env, DATABASE_URL: undefined, ...env } },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
Not checked against OSV yet; the weekly check has not reached this version.
What would make this Verified
6 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim filelayer: 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.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.