Security & Sandboxing
Benchtop Labs prioritizes the safety and integrity of modern developer environments. All package installations, build assertions, and benchmark test suites are executed in strictly isolated container sandboxes.
1. Containerized Sandbox Isolation
Every automated bench verification runs inside a dedicated, ephemeral Linux container. Before running package commands, root privileges are stripped, memory and CPU quotas are locked, and host file system mounting is disabled. Once the execution completes, the container is destroyed immediately.
2. Dependency Hygiene & Package Audits
Our automated verification checks analyze dependency graphs to identify packages with excessive sub-dependencies or known supply chain vulnerabilities. We champion software with lean dependency footprints to minimize supply chain exposure for end users.
3. Reproducible Build & Release Verification
We verify that released package binaries and wheels correlate directly with tagged Git releases on official repositories. This helps guard against package tampering or unauthorized registry publication.
4. Responsible Vulnerability Disclosure
If you discover a security vulnerability in the Benchtop Labs website, its verification harness, or any of our founding tools, please notify us responsibly:
- Direct security notification to founder Ameya Kulkarni on GitHub (@Ameya79) or via LinkedIn.
- Security advisories may also be opened directly on the relevant evaluated tool's upstream repository.
We acknowledge receipt within 48 hours and coordinate remediation before public disclosure.