contextport@1.0.0
CAUTION· static onlyPublisher claims: "Enables AI coding sessions to save task progress, decisions, next steps, and verification evidence as local snapshots, then resume with file-change and freshness checks. It supports evidence-aware handoffs without running tests or calling model APIs." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
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 code
- What the honeypot saw
- nothing has run yet
- What we could not test
- everything: the server has not run yet
Run it before you trust it. Nothing has run yet: the code was read, the server was not. `vet-skills try` runs this exact version in the honeypot in about a minute.
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 analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 60/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: Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
for (const p of ["../x", "/etc/passwd", "a/../../x", "a\\b"])Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const c = await port.create({ goal: "x", files: ["new.ts", ".env"] });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.copy("npx --yes @batype/[email protected] --help", "install")Fix: Pin versions and sources; vendor anything fetched at install time.await symlink("/etc/passwd", path.join(root, "link"));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./(^|\/)(?:\.env(?:\..*)?|\.git|\.contextport|node_modules|\.ssh|\.aws|credentials(?:\..*)?|.*\.(?:pem|key|p12|pfx))($|\/)/i;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.await writeFile(path.join(root, ".env"), "SECRET=private");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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim batype: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Access to sensitive file paths≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.