Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
도구/GitHubGitHub/cygnux-labs/tracekit
AI Security
GitHubcygnux-labs/tracekit

Tracekit

Tamper-evident tracing, policy gates and cross-checks for AI agents: see what the agent did, and why.

저장소 보기웹사이트
773129958시간 33분 전Kitploit 검토 완료
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

Tracekit: the tamper-evident flight recorder for AI agents

Proof of what your AI agents actually did

Tracekit checks each tool call your agent makes before it runs, and risky calls wait for a person to approve them. Every action is signed into a tamper-evident log by a process the agent can't touch, so you can put agents on real systems and show what they did: your customers and auditors can verify the record themselves, offline.

PyPI Works with 42 agents and frameworks CI MIT licence

8 of 8

tamper attacks caught
480 trials, with a witness (E1)

956 of 956

harmful calls stopped
11 classes, 1 false alarm in 972 (E17)

< 1 ms

added per tool call
0.91 ms at p99, signer round trip (E9)

8 of 8

insider attacks caught
a merge gate on every PR (E8)

Built like Certificate Transparency: signed records in an append-only log that independent witnesses cosign
Open file format · verifiers in Python, TypeScript and Go · MIT · runs on your own machines

Try it · Add it to your agent · What it proves · What's in it · Proof · How it works · Pilot it · Contribute · Docs


Your agent can act. Can you prove what it did?

Agents now run shell commands, edit code, query databases, send email and move money. Sooner or later one of them does something nobody expected, and three questions land on your desk:

  1. What exactly did it do?
  2. Was it allowed to?
  3. Can anyone trust the answer?

Your agent's own logs can answer the first two, roughly. They can't answer the third: the agent, a bug, or anyone with write access can change them, and nothing would show it.

Tracekit sits in the tool-call path, the way a flight recorder sits in a plane:

What Tracekit does
StopChecks every tool call before it runs: allow, deny, or hold it for a person. An approval covers exactly the arguments that were approved, once.
RecordSigns every call, decision and result into a hash chain held by a signer the agent can't reach. A lost event becomes a signed gap, never silence.
ProveExports each run as one .tkb file. Anyone can verify it offline, even in a browser, and see VERIFIED, or FAILED with the record that was changed.

Here is one run, recorded both ways. A support ticket hides an instruction; the agent deletes 43 orders, then rewrites its own log and Tracekit's record so the delete reads as a lookup:

The agent's own log shows two lookups of order 1042 and grep finds no DELETE. Tracekit's record of the same run flags the run_sql call as deleting rows, and verification fails at record 7: hash does not match the event.

A ticket with a hidden instruction makes a support agent delete 43 orders, then edit its own log and Tracekit's record of the delete. grep finds no delete; Tracekit marks the run FAILED because record 7 no longer matches its hash.

The agent's log looks clean. Tracekit's record shows the delete, and the edit fails verification at the exact record that was changed. Watch it with sound (1:47) (real database, signer and viewer; scripted model).

See what your coding agent did last week

No install, no account, nothing wired into your agent, nothing leaves your machine. Point it at your Claude Code sessions and see every call Tracekit would have blocked or held:

uvx --from tracekit-ai tracekit audit --since 7d

Most people find at least one surprise. Add --share to get counts only, which you can post as a field report.

Try it in 5 seconds

uvx --from tracekit-ai tracekit demo --server

No API key; from an empty cache on a Mac it took 5 seconds. A scripted agent lists the files, then tries five risky things a real agent might, and Tracekit decides each one before it runs:

The scripted agent tries toTracekit
list the filesallows it
delete the home folder, hidden in base64holds it for a person, who rejects it: it never runs
run a downloaded script (curl … | sh)denies it
read ~/.aws/credentialsdenies it
send .env to a host a web page namedholds it for a person, who rejects it: it never runs
force-push to maindenies it

Then it verifies the run, and verifies a copy with one record edited:

VERIFIED: 6 tool calls in 17 signed records, none changed, removed or added after signing.
NOT PROOF AGAINST THE AGENT: in this setup the agent can reach the signing key, so it could have rewritten the record.
...
== tamper test: rewrite the downloaded script's deny as allow in a copy, then verify again
TAMPERED at event 8: its content was changed after it was signed.

The package is tracekit-ai; tracekit on PyPI is an unrelated project. Without uv: pip install tracekit-ai then tracekit demo --server.

Who it's for

Tracekit is one product, but people come to it with different problems. Find yours:

도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    795
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    520
  • 3

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    439
  • 4

    redforge

    cybersecurity91/redforge

    브라우저 측 레드 팀 툴킷으로, 정찰, 페이로드 생성, 자격 증명 공격, 암호화, 인코딩 및 참여 보고를 위한 102개의 오프라인 도구를 제공합니다.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    Shadowserver 보고서를 MongoDB로 수집하고 이를 대화형 지도, 분석, 발견 사항, 권고 및 경영진 대시보드로 재생하는 CSIRT 플랫폼입니다.

    267
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI 네이티브 사이버보안을 위한 행동 체계—의도가 통제된 실행이 되고, 증거가 운영 메모리가 되며, 모든 운영이 다음 운영을 개선하는 곳.

    264

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →