valca 0.3.0__tar.gz

valca-0.3.0/AUTHORS

@@ -0,0 +1 @@
+Prem Kumar Akula

valca-0.3.0/LICENSE

@@ -0,0 +1,73 @@
+Business Source License 1.1
+
+Parameters
+
+Licensor:             Prem Kumar Akula
+Licensed Work:        Vigil
+                      The Licensed Work is (c) 2026 Prem Kumar Akula
+Additional Use Grant: You may make production use of the Licensed Work,
+                      provided such use does not include offering the Licensed
+                      Work to third parties on a hosted or embedded basis in
+                      order to compete with Vigil's paid commercial offerings.
+Change Date:          Four years from the date the specific Licensed Work
+                      version is first publicly distributed under this License.
+Change License:       MIT License
+
+For information about alternative licensing arrangements for the Licensed
+Work, please contact: https://github.com/vigilsec-io/cordon/issues
+
+Notice
+
+The Business Source License (this document, or the "License") is not an Open
+Source License, as defined by the Open Source Initiative. However, the
+Licensed Work will eventually be made available under an Open Source License,
+as stated in this License.
+
+License text copyright (c) 2017 MariaDB Corporation Ab, All Rights Reserved.
+"Business Source License" is a trademark of MariaDB Corporation Ab.
+
+-----------------------------------------------------------------------------
+
+Business Source License 1.1
+
+Terms
+
+The Licensor hereby grants you the right to copy, modify, create derivative
+works, redistribute, and make non-production use of the Licensed Work. The
+Licensor may make an Additional Use Grant, above, permitting limited
+production use.
+
+Effective on the Change Date, or the fourth anniversary of the first publicly
+available distribution of a specific version of the Licensed Work under this
+License, whichever comes first, the Licensor hereby grants you rights under
+the terms of the Change License, and the rights granted in the paragraph
+above terminate.
+
+If your use of the Licensed Work does not comply with the requirements
+currently in effect as described in this License, you must purchase a
+commercial license from the Licensor, its affiliated entities, or authorized
+resellers, or you must refrain from using the Licensed Work.
+
+All copies of the original and modified Licensed Work, and derivative works
+of the Licensed Work, are subject to this License. This License applies
+separately for each version of the Licensed Work and the Change Date may vary
+for each version of the Licensed Work released by Licensor.
+
+You must conspicuously display this License on each original or modified copy
+of the Licensed Work. If you receive the Licensed Work in original or
+modified form from a third party, the terms and conditions set forth in this
+License apply to your use of that work.
+
+Any use of the Licensed Work in violation of this License will automatically
+terminate your rights under this License for the current and all other
+versions of the Licensed Work.
+
+This License does not grant you any right in any trademark or logo of
+Licensor or its affiliates (provided that you may use a trademark or logo of
+Licensor as expressly required by this License).
+
+TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON
+AN "AS IS" BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS,
+EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
+TITLE.

valca-0.3.0/NOTICE

@@ -0,0 +1,16 @@
+Valca (formerly published as Vigil / vigilsec)
+Copyright (c) 2026 Prem Kumar Akula. All rights reserved.
+
+Created: 2026-06-26
+Author: Prem Kumar Akula
+
+This software and all associated ideas, algorithms, rule definitions,
+and product concepts are the exclusive intellectual property of
+Prem Kumar Akula.
+
+The VGL-D001 rule (docker-compose port binding to 0.0.0.0 without
+127.0.0.1 prefix) represents a novel detection approach not implemented
+by any known IaC scanning tool as of the creation date above.
+
+Commercial use requires a separate license agreement.
+Contact: https://github.com/vigilsec-io/cordon/issues

valca-0.3.0/PKG-INFO

@@ -0,0 +1,430 @@
+Metadata-Version: 2.4
+Name: valca
+Version: 0.3.0
+Summary: AI coding security co-pilot — blocks insecure code at generation time
+Author: Prem Kumar Akula
+License: Business Source License 1.1
+        
+        Parameters
+        
+        Licensor:             Prem Kumar Akula
+        Licensed Work:        Vigil
+                              The Licensed Work is (c) 2026 Prem Kumar Akula
+        Additional Use Grant: You may make production use of the Licensed Work,
+                              provided such use does not include offering the Licensed
+                              Work to third parties on a hosted or embedded basis in
+                              order to compete with Vigil's paid commercial offerings.
+        Change Date:          Four years from the date the specific Licensed Work
+                              version is first publicly distributed under this License.
+        Change License:       MIT License
+        
+        For information about alternative licensing arrangements for the Licensed
+        Work, please contact: https://github.com/vigilsec-io/cordon/issues
+        
+        Notice
+        
+        The Business Source License (this document, or the "License") is not an Open
+        Source License, as defined by the Open Source Initiative. However, the
+        Licensed Work will eventually be made available under an Open Source License,
+        as stated in this License.
+        
+        License text copyright (c) 2017 MariaDB Corporation Ab, All Rights Reserved.
+        "Business Source License" is a trademark of MariaDB Corporation Ab.
+        
+        -----------------------------------------------------------------------------
+        
+        Business Source License 1.1
+        
+        Terms
+        
+        The Licensor hereby grants you the right to copy, modify, create derivative
+        works, redistribute, and make non-production use of the Licensed Work. The
+        Licensor may make an Additional Use Grant, above, permitting limited
+        production use.
+        
+        Effective on the Change Date, or the fourth anniversary of the first publicly
+        available distribution of a specific version of the Licensed Work under this
+        License, whichever comes first, the Licensor hereby grants you rights under
+        the terms of the Change License, and the rights granted in the paragraph
+        above terminate.
+        
+        If your use of the Licensed Work does not comply with the requirements
+        currently in effect as described in this License, you must purchase a
+        commercial license from the Licensor, its affiliated entities, or authorized
+        resellers, or you must refrain from using the Licensed Work.
+        
+        All copies of the original and modified Licensed Work, and derivative works
+        of the Licensed Work, are subject to this License. This License applies
+        separately for each version of the Licensed Work and the Change Date may vary
+        for each version of the Licensed Work released by Licensor.
+        
+        You must conspicuously display this License on each original or modified copy
+        of the Licensed Work. If you receive the Licensed Work in original or
+        modified form from a third party, the terms and conditions set forth in this
+        License apply to your use of that work.
+        
+        Any use of the Licensed Work in violation of this License will automatically
+        terminate your rights under this License for the current and all other
+        versions of the Licensed Work.
+        
+        This License does not grant you any right in any trademark or logo of
+        Licensor or its affiliates (provided that you may use a trademark or logo of
+        Licensor as expressly required by this License).
+        
+        TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON
+        AN "AS IS" BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS,
+        EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
+        MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
+        TITLE.
+        
+Project-URL: Homepage, https://valca.io
+Project-URL: Source, https://github.com/vigilsec-io/cordon
+Project-URL: Issues, https://github.com/vigilsec-io/cordon/issues
+Keywords: security,devsecops,docker,ai,claude,static-analysis,linter
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+License-File: AUTHORS
+Dynamic: license-file
+
+# Valca
+
+**AI coding security co-pilot — blocks insecure code at the moment of generation.**
+
+> **Formerly published as `vigilsec`.** The package is now `valca`. Both the `valca` and `vigil`
+> commands work, so existing hooks and scripts keep running unchanged.
+
+Valca intercepts every file an AI coding assistant writes and blocks it if CRITICAL or HIGH security findings are detected — before the file hits disk. It's the only tool that operates at generation time rather than post-commit.
+
+```
+AI writes file → vigil scan → exit 2 → Claude Code blocks the write
+```
+
+---
+
+## The Problem
+
+AI coding assistants reproduce the most common patterns in their training data. The most common patterns are insecure defaults.
+
+The clearest example: every existing IaC scanner (Checkov, Trivy, Snyk, Semgrep) misses the docker-compose port binding that exposes your database to the internet:
+
+```yaml
+ports:
+  - "5432:5432"   # ← binds to 0.0.0.0, bypasses UFW, reachable from anywhere
+```
+
+The correct form is `"127.0.0.1:5432:5432"`. Vigil catches it. Nothing else does.
+
+---
+
+## Install
+
+```bash
+pip install valca
+```
+
+**Wire the Claude Code hook (one time):**
+
+```bash
+valca init --global     # `vigil init --global` also works
+```
+
+That's it. Every file Claude Code writes is now scanned before it saves. Reload Claude Code to activate.
+
+---
+
+## Network access
+
+Valca's core scanning is fully offline — the package has **zero runtime dependencies** and the
+engine never sends your code, file paths, or findings anywhere.
+
+Three rules do reach the network, because checking whether a dependency is vulnerable or fabricated
+is impossible offline. When a manifest (`requirements.txt`, `package.json`, lockfiles) is scanned,
+these rules send **package names and version strings only** to:
+
+| Host | Used by | What is sent |
+|---|---|---|
+| `api.osv.dev` | VGL-PKG001 (known CVE in a pinned version) | package name + version |
+| `pypi.org` | VGL-PKG002/003/004 (hallucinated, stale, or suspicious package) | package name |
+| `registry.npmjs.org` | VGL-PKG002/003/004 | package name |
+
+Your source code, file contents, file paths, and scan results are never transmitted. If your
+dependency inventory is itself sensitive, turn these rules off in `.vigilrc` and Valca runs
+completely offline:
+
+```ini
+disabled_rules = ["VGL-PKG001", "VGL-PKG002", "VGL-PKG003", "VGL-PKG004"]
+```
+
+---
+
+## Usage
+
+```bash
+# Scan a single file
+vigil scan docker-compose.yml
+
+# Scan a directory
+vigil scan ./my-project/
+
+# JSON output (for CI / dashboards)
+vigil scan ./my-project/ --format json
+
+# SARIF output (for GitHub Advanced Security)
+vigil scan ./my-project/ --format sarif > results.sarif
+
+# Only report HIGH and above
+vigil scan ./my-project/ --severity HIGH
+
+# Open feedback & waitlist form
+vigil feedback
+```
+
+**Exit codes:**
+
+| Code | Meaning |
+|------|---------|
+| `0` | No findings — write proceeds |
+| `1` | Advisory findings only (MEDIUM / LOW / INFO) |
+| `2` | CRITICAL or HIGH found — **Claude Code blocks the write** |
+
+---
+
+## See It in Action
+
+**Blocking a vulnerable GitHub Actions workflow at write time:**
+
+<!-- GIF: terminal showing claude writing ai-review.yml → vigil hook fires → BLOCKED + VGL-GHA009 CRITICAL → fix applied → clean -->
+![Vigil blocking Comment and Control attack](docs/demo-gha.gif)
+
+In April 2026, researchers found that all three major AI coding agents (Claude Code, Gemini CLI, Copilot) could be hijacked to exfiltrate `ANTHROPIC_API_KEY` and `GITHUB_TOKEN` via a hidden HTML comment in a GitHub issue. CVSS 9.4. No special access required.
+
+Vigil catches the vulnerable workflow (`issues:` trigger + AI agent + API key in env) before it reaches git — the only tool that does.
+
+→ [Full writeup: The Attack That Steals Your API Keys Through a GitHub Issue Comment](https://medium.com/@rjbdjnf/the-attack-that-steals-your-api-keys-through-a-github-issue-comment-b0301c1906dc)
+
+---
+
+## Rules
+
+36 rules across 9 categories. All built-in, stdlib-only, zero runtime dependencies.
+
+### Secrets & Injection (10 rules)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-S001 | CRITICAL | Hardcoded AWS / cloud API keys |
+| VGL-S002 | CRITICAL | Hardcoded passwords (`password =`, `passwd =`) |
+| VGL-S003 | HIGH | Generic API key / token assignments |
+| VGL-S004 | HIGH | Generic secret / credential assignments |
+| VGL-S005 | CRITICAL | JWT signing secrets |
+| VGL-S006 | CRITICAL | PEM private keys |
+| VGL-S007 | CRITICAL | Credential-embedded database URLs (`postgres://user:pass@host`) |
+| VGL-S008 | CRITICAL | Stripe live keys (`sk_live_...`) |
+| VGL-S009 | CRITICAL | Slack tokens (`xoxb-`, `xoxp-`) |
+| VGL-S010 | CRITICAL | OpenAI, GitHub, GitLab, Google provider keys |
+| VGL-I001 | CRITICAL | `eval()` with variable input |
+| VGL-I002 | HIGH | `subprocess(shell=True)` with variable input |
+| VGL-I003 | HIGH | `os.system()` with variable input |
+
+### Docker IaC (2 rules)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-D001 | CRITICAL | `"PORT:PORT"` binding — bypasses UFW, exposes to internet |
+| VGL-D002 | HIGH | Hardcoded secrets in `environment:` blocks |
+
+### Dockerfile Hardening (3 rules)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-DF001 | HIGH | Container running as root (no `USER` directive) |
+| VGL-DF002 | MEDIUM | Unpinned `:latest` base image |
+| VGL-DF003 | CRITICAL | Secrets baked into image layers via `ENV`/`ARG` |
+
+### nginx (1 rule)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-N001 | HIGH | Missing security headers, `server_tokens on`, deprecated TLS |
+
+### Kubernetes (1 rule)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-K001 | CRITICAL/HIGH | `privileged: true`, `hostNetwork/hostPID/hostIPC: true` |
+
+### IAM Policies (1 rule)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-IAM001 | CRITICAL/HIGH | `"Action": "*"` and `"Resource": "*"` wildcards |
+
+### AI Agent Patterns (7 rules)
+
+New category — catches the security anti-patterns unique to AI-generated agentic code.
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-A001 | CRITICAL | LLM output piped to `subprocess.run()` / `os.system()` |
+| VGL-A002 | HIGH | Hardcoded `auto_approve = True` / `skip_confirmation = True` |
+| VGL-A003 | HIGH | Unbounded `while True` loop making LLM calls with no iteration cap |
+| VGL-A004 | HIGH | LLM response content written directly to filesystem |
+| VGL-PI001 | CRITICAL | User input embedded in system prompt |
+| VGL-PI002 | HIGH | Raw `request.body` passed as LLM message content |
+| VGL-PI003 | HIGH | `str.format()` on `system_prompt` variables with user-controlled data |
+| VGL-PI004 | MEDIUM | Unsanitized tool output appended to conversation |
+
+### MCP Server Security (3 rules)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-MCP001 | CRITICAL | Injection strings in tool descriptions (`ignore previous instructions`) |
+| VGL-MCP002 | HIGH | Dynamic tool descriptions built from user-controlled data |
+| VGL-MCP003 | HIGH | Shell execution inside MCP handlers without a sandbox |
+
+### Shell Scripts (1 rule)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-S011 | HIGH | Secret variable passed inline to subprocess or SSH command — visible in `ps aux` on both machines |
+
+### Dependency CVEs (2 rules)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-DEP001 | HIGH | Python CVEs via `pip-audit` (runs on every `requirements.txt` change) |
+| VGL-DEP002 | HIGH | npm CVEs via `npm audit` (runs on every `package.json` change) |
+
+### Trivy IaC Deep Scan (1 rule)
+
+| Rule | Severity | What it catches |
+|------|----------|----------------|
+| VGL-T001 | HIGH | Dockerfile and Terraform misconfigurations via Trivy |
+
+---
+
+## Configuration
+
+Place a `.vigilrc` file in your project root (or any ancestor directory):
+
+```toml
+# .vigilrc
+disabled_rules = ["VGL-T001"]        # skip trivy scan for this project
+min_severity   = "HIGH"              # only report HIGH and above
+exclude_paths  = ["vendor", "legacy"]
+telemetry      = false               # opt out of anonymous local telemetry
+```
+
+Vigil walks up the directory tree to find the nearest `.vigilrc`. Child config always wins over parent. Monorepos can have per-project overrides alongside a workspace default.
+
+**Inline suppression** — for a specific line you've reviewed and accepted:
+
+```python
+auto_approve = True  # vigil: ignore
+```
+
+Same pattern as `# noqa` (flake8) and `# nosec` (bandit).
+
+---
+
+## Opt-out
+
+Vigil collects anonymous, local-only telemetry: rule ID, severity, and file extension. No file paths, no code, no identifiable data. Stored at `~/.vigil/events.jsonl` — never sent anywhere.
+
+Opt out permanently:
+
+```bash
+export VIGIL_NO_TELEMETRY=1
+```
+
+Or in `.vigilrc`:
+
+```toml
+telemetry = false
+```
+
+---
+
+## Adding a Rule
+
+```python
+# src/vigil/rules/my_category.py
+from pathlib import Path
+from .base import Finding, Rule, Severity
+
+class MyRule(Rule):
+    id = "VGL-X001"
+    name = "Descriptive rule name"
+    severity = Severity.HIGH
+
+    def applies_to(self, path: Path) -> bool:
+        return path.suffix == ".yml"
+
+    def check(self, path: Path) -> list[Finding]:
+        findings = []
+        for i, line in enumerate(path.read_text().splitlines(), 1):
+            if "bad_pattern" in line:
+                findings.append(Finding(
+                    rule_id=self.id,
+                    severity=self.severity,
+                    message="Found bad pattern",
+                    file_path=path,
+                    line=i,
+                    snippet=line.strip(),
+                    fix="Do this instead.",
+                ))
+        return findings
+```
+
+Then add it to `DEFAULT_RULES` in `src/vigil/rules/__init__.py`. Write tests. Done.
+
+---
+
+## GitHub Actions
+
+Add Vigil to any CI pipeline — copy `vigil-action/workflow-template.yml` into your project's `.github/workflows/vigil.yml`:
+
+```yaml
+- name: Install Vigil
+  run: pip install valca --quiet
+
+- name: Scan with Vigil
+  run: vigil scan . --no-color
+
+- name: Upload SARIF to GitHub Code Scanning
+  uses: github/codeql-action/upload-sarif@v3
+  with:
+    sarif_file: vigil-results.sarif
+```
+
+Findings appear as inline annotations on PR diffs in the GitHub Security tab.
+
+---
+
+## Development
+
+```bash
+git clone https://github.com/vigilsec-io/cordon.git
+cd vigil
+python3 -m venv venv && source venv/bin/activate
+pip install -e ".[dev]"
+pytest tests/ -v
+```
+
+---
+
+## License
+
+[Business Source License 1.1](LICENSE) — free for non-commercial use. Commercial use requires a license agreement. Converts to MIT on 2030-06-26.
+
+---
+
+## Feedback
+
+Found a false positive? Want a rule that doesn't exist yet? Building with AI agents and hitting patterns Vigil should catch?
+
+[Open an issue → github.com/vigilsec-io/cordon/issues](https://github.com/vigilsec-io/cordon/issues)
+
+Or: `vigil feedback`