Security
Threat Model
Section titled “Threat Model”What Code Bearings touches
Section titled “What Code Bearings touches”- Local filesystem (read-only): Reads TypeScript/JavaScript source files via AST parsing (ts-morph). Does not modify source files.
- SQLite database (read/write): Creates and writes to
.code-bearings/bearings.dbin your project directory. This is the only file Code Bearings writes. - Git CLI (read-only): Executes
git diffandgit rev-parseto detect changes. Does not modify git state.
What Code Bearings does NOT touch
Section titled “What Code Bearings does NOT touch”- No network access
- No telemetry, analytics, or phone-home
- No cloud services or API keys
- No file modification outside
.code-bearings/ - No access to files outside your project directory
- No execution of user code — static analysis only
No Telemetry
Section titled “No Telemetry”Code Bearings does not collect, transmit, or store any telemetry, usage data, or analytics. This is by design and will not change.
VS Code Extension
Section titled “VS Code Extension”- Webview panel uses
enableScripts: truefor interactive features - Scripts are injected by the extension, not loaded from external sources
retainContextWhenHidden: truepreserves review state across tab switches- The extension reads files via the VS Code API — same read-only contract as the CLI
Reporting Vulnerabilities
Section titled “Reporting Vulnerabilities”Email: 64996768+mcp-tool-shop@users.noreply.github.com
- Acknowledgment within 48 hours
- Initial assessment within 7 days
- Fix or mitigation within 30 days for confirmed vulnerabilities