jevelry@0.7.0
VERIFIED· install onlyPublisher claims: "Use Jev everywhere to make & track decisions" 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
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-12 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
… smaller or local one might do | `npx jevelry ask request-route --state @request.json` | `complexity` at level 0 and `needs_tools` no: send it to the small model | send it to the large model | send it to the large model | | you finished wo…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… a report to the CI owner or a fix | `npx jevelry run failing-test --state @test.json` | the shipped commands only print the next step for the `cause`: rerun with `retries`, report it to the CI owner, or fix the code; replace them with you…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return discoveryDirs({ cli: cli ?? [], ...env ? { env } : {}, cwd: process.cwd(), home: home() });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…s into the app you are building | `npx jevelry ask ticket-triage --state @ticket.json` | route it to the `team`, and `urgent` yes puts it on top of the queue | route it and flag it for the queue owner | leave it i…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.npx jevelry installFix: Pin versions and sources; vendor anything fetched at install time.… you are unsure whose it is | `npx jevelry ask escalation-route --state @request.json` | send it to the `route` it names | send it and copy the shared inbox | leave it for a person to route | | an alert fire…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.npx jevelry models --localFix: Pin versions and sources; vendor anything fetched at install time.…oes that part alone. To run Jev on the machine instead of the hosted API, run `npx jevelry models --local`, which ranks the decision models on Hugging Face and says for e…Fix: Pin versions and sources; vendor anything fetched at install time.…nds on your pull request | `npx jevelry ask review-comment-kind --state @comment.json` | `defect`: fix the code, `environment`: fix or report the CI or the sandbox and leave the code alone, `style`: fold it into a cleanup pass | do the sam…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…om then on every ask goes to a local `llama-server` that the first ask starts. `npx jevelry stop` stops it, and `npx jevelry install --typesafe` goes back to hosted Jev. T…Fix: Pin versions and sources; vendor anything fetched at install time.const { jevel: loaded } = loadJevel(name, discoveryDirs({ cli: options.jevels ?? [], ...env ? { env } : {}, cwd: process.cwd(), home }));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const { TYPESAFE_API_KEY: _key, ...env } = process.env;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx jevelry install --local vllm-d3-flashFix: Pin versions and sources; vendor anything fetched at install time.env: { ...env, JEVELRY_STATE: file, JEVELRY_DECISION: meta.decision, JEVELRY_OPTION: meta.option ?? "", JEVELRY_LOG_ID: meta.logId ?? "" }Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…a terminal it changes nothing and names both ways. If you only need the skill, `npx jevelry install-skill` does that part alone. To run Jev on the machine instead of the …Fix: Pin versions and sources; vendor anything fetched at install time.npx jevelry installFix: Pin versions and sources; vendor anything fetched at install time.- "Dan called the plan unworkable"Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.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
No advisories in OSV for jevelry@0.7.0 as of 44 h ago. This is the package itself, not its dependencies.