ts-backtest@0.1.0
VERIFIED· install onlyPublisher claims: "Enables users to prepare and validate market data, launch and control backtests, and retrieve results, causal explanations, and self-contained reports through stdio tools. It also supports polling or canceling jobs and running sweep, walk-forward, factor, and study research workflows with bounded pagination and reproducible artifacts." 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: Verified 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 nodejs.org — 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-12 and scored it 88/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
await writeFile(join(f.workspace, 'large.json'), JSON.stringify(minuteInput(30_000)));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.assertThat(flags.size===2&&flags.has('--input')&&flags.has('--output'),'INVALID_ARGUMENTS','report requires exactly --input result.json --output report.html');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.await writeFile(join(f.workspace, 'large.json'), JSON.stringify(minuteInput(30_000)));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const output=resolve(root,quick?'benchmark-output/quick-benchmark.json':finalHot?'docs/evidence/benchmark-final-hot.json':'docs/evidence/benchmark.json');await mkdir(dirname(output),{recursive:true});Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.run([join(release,'cli.cjs'),'run','--config',join(release,'examples/basic.json'),'--output',resultFile]);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.await mkdir(workspace); await writeFile(join(workspace, 'bars.json'), JSON.stringify(input()));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…dies(this.storeDir); await atomicJSON(resolve(this.storeDir, 'store-policy.json'), { schemaVersion: '1', retention: 'until-explicit-cleanup', maxStoreBytes: this.options.maxStoreBytes, quotaIncludes: ['datasets', 'plans', 'runs', 'studies'…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…((n, info) => n + info.bytes, 0); await writeFile(resolve(directory, 'manifest.json'), JSON.stringify({ version: packageInfo.version, buildNode: process.version, buildPlatform: `${process.platform}-${process.arch}`, sourceLockSha256: creat…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.artifacts['resolved-input.json'] = await artifactIO.writeJSON(join(staging, 'resolved-input.json'), input, undefined, budget);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.await writeFile(join(f.workspace, 'large.json'), JSON.stringify(minuteInput()));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… as const; const usage = { commands: ['capabilities', 'prepare --config config.json [--output dataset.cache.json]', 'inspect --config config.yaml', 'inspect --dataset dataset.cache.json', 'validate --config config.yaml', 'run --config conf…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.await writeFile(join(f.root, 'outside.json'), JSON.stringify(input())); await symlink(join(f.root, 'outside.json'), join(f.workspace, 'escape.json'));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.import { mkdir, readdir, readFile, writeFile, cp, rm, stat, chmod } from 'node:fs/promises';Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.await writeFile(join(configDir, 'metadata.json'), JSON.stringify(input().metadata));Fix: 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.