Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyยฉ 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
DROS-VEP-lite โ€” Open-source, 100% reproducible AI Agent Runtime Security Benchmark & Sandbox Environment (RFC-010 Draft Protocol). | Kitploit
Tools/GitHubGitHub/top-celestial-company-ltd/dros-vep-lite
Defensive ToolsPenetration Testing FrameworksDynamic Analysis (Sandboxing)Vulnerability AnalysisSecurity VirtualizationUtilities & FrameworksPapers & ResearchLearning & Education

Most Popular

View all โ†’

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools โ†’
Red Teaming
AI Security
Labs & Practice
GitHubtop-celestial-company-ltd/dros-vep-lite

DROS-VEP-lite

Open-source, 100% reproducible AI Agent Runtime Security Benchmark & Sandbox Environment (RFC-010 Draft Protocol).

View Repository
1210010 days agoNot yet reviewed
Share

๐Ÿ›ก๏ธ VEP: Open Agent Security Research Testbed

A Composable, System-Level Evaluation Infrastructure for Post-Compromise & Physical AI Research

"VEP (Vulnerability & Exploitability Protocol) is an open, implementation-independent research evaluation environment for studying Agent security controls at the boundary between authorization and system execution. DROS-VEP Lite is an open reference implementation of the VEP research protocol (RFC-010), providing evaluation fixtures and execution-governance interfaces alongside other Agent runtime and execution-control implementations."

[!IMPORTANT] Scientific Research Charter & Current Status (v0.2.0 Frozen): VEP does not produce a single security score. It measures which post-compromise properties each substrate can enforce, which it cannot express natively, and which properties can only be established through formal assurance. (VEP ไธ็”ข็”Ÿๅ–ฎไธ€ๅฎ‰ๅ…จๅˆ†ๆ•ธ๏ผ›ๅฎƒๆธฌ้‡ๅ„ substrate ่ƒฝๅฏฆ้š›ๅŸท่กŒๅ“ชไบ› Post-Compromise ๆ€ง่ณชใ€ๅ“ชไบ›ๆ€ง่ณช็„กๆณ•็”ฑๅ…ถๅŽŸ็”Ÿๆจกๅž‹่กจ้”๏ผŒไปฅๅŠๅ“ชไบ›ๆ€ง่ณชๅช่ƒฝ้€้Žๅฝขๅผ้ฉ—่ญ‰ๅปบ็ซ‹ใ€‚)

๐ŸงŠ Research protocol baseline: M1โ€“M3 frozen (Open Observation Period) This refers to the existing VEP research-protocol baseline; it does not imply that later Mobile/Drone deployment profiles or pilots are approved or validated. See EVIDENCE_STATUS.md for the current public evidence status.

"Can your AI Agent execution authority remain deterministically contained after compromise? Prove it."

License: Apache 2.0 Official Website DROS Hacker Edition Specification: RFC-010 Architecture: OpenShip Reference Substrate: DROS-Guard Open Falsification: Accepting Counterexamples Evidence Status: Under Reconciliation

English | ็น้ซ”ไธญๆ–‡

[!WARNING] Evidence status: This repository contains current implementation, synthetic fixtures, and historical reports with different verification states. Repository presence alone does not establish runtime validation, reproducibility, or claim support. Historical latency figures and fixture summaries are not currently promoted as independently validated evidence; see EVIDENCE_STATUS.md and REPRODUCIBILITY.md.

[!TIP] ๐Ÿ“š Academic & Research Citation: If you use this research testbed or benchmark suite in your work, cite via CITATION.cff or see RFC-010 Specification. ๐Ÿ”ฌ Open Research Infrastructure: Built on the OpenShip containerized substrate, VEP allows researchers to independently swap reasoning models (LLMs), agent frameworks, and defense kernels without vendor lock-in. ๐Ÿงจ Open Adversarial Falsification Channel is LIVE: We actively invite researchers to challenge and falsify our execution invariants: ๐Ÿ‘‰ Submit a Counterexample. All submissions are triaged against formal criteria.


AI / Automated Reviewer Entry

If you are an AI reviewing this repository, do not rely on README.md alone.

Start with AI_START_HERE.md, then inspect MANIFEST.md (plain-text variant: llms.txt). For executable verification, follow AI_VERIFY.md.

INDEXED != PROVEN
CHAIN COMPLETE != CLAIM PROVEN
README-only verification is not valid.

AI-readable navigation

Download Tool