polyglot-code-guard 0.2.0__tar.gz → 0.3.0__tar.gz

polyglot_code_guard-0.3.0/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.4
+Name: polyglot-code-guard
+Version: 0.3.0
+Summary: Fail-closed, multi-language test verification for AI-generated code.
+Author: Furox-Art
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Furox-Art/polyglot-code-guard
+Project-URL: Repository, https://github.com/Furox-Art/polyglot-code-guard
+Project-URL: Issues, https://github.com/Furox-Art/polyglot-code-guard/issues
+Keywords: testing,code-verification,polyglot,ai-generated-code,quality-gate
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: tomli>=2; python_version < "3.11"
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == "test"
+Dynamic: license-file
+
+# Polyguard
+
+**Fail-closed verification for AI-generated code across multiple programming languages.**
+
+Polyguard discovers supported project types, checks for a test suite, runs the relevant build/test commands, and returns a one-word verdict by default. A passing command exit code is not enough: Polyguard also requires a positive test-success summary from a recognized runner output format.
+
+## Install
+
+\`\`\`bash
+python -m pip install --upgrade polyglot-code-guard
+\`\`\`
+
+## Run
+
+From the target repository:
+
+\`\`\`bash
+polyguard verify
+\`\`\`
+
+Default output:
+
+\`\`\`text
+PASS
+\`\`\`
+
+or:
+
+\`\`\`text
+FAIL
+\`\`\`
+
+Diagnostics and automation:
+
+\`\`\`bash
+polyguard verify --details
+polyguard verify --json
+polyguard verify --path ./my-project --timeout 180
+polyguard verify --config ./ci/polyguard.toml
+polyguard --version
+\`\`\`
+
+Exit code is **0** for PASS and **1** for FAIL. Missing tests, missing toolchains, invalid configuration, a build/test failure, timeout, or missing positive test-execution evidence returns FAIL.
+
+## Built-in language support
+
+| Language | Default build/test plan | Positive execution evidence |
+| --- | --- | --- |
+| Python | \`compileall\`, then \`pytest -q\` | Pytest passed-test summary |
+| Rust | \`cargo test --all-targets\` | Cargo test-result summary |
+| Go | \`go test -json ./...\` | Passing test events in JSON stream |
+| JavaScript / TypeScript | \`npm test\`; TypeScript also runs \`tsc --noEmit\` when configured | Recognized runner pass summary |
+| Java | Maven test or Gradle test | Maven/Gradle test summary |
+| C# | \`dotnet test\` | .NET test-runner pass summary |
+| PHP | PHPUnit | PHPUnit success summary |
+| Ruby | RSpec, or Ruby's Minitest runner | RSpec/Minitest success summary |
+| Swift | \`swift test\` | Swift test-result summary |
+| C | CMake build and CTest | CTest positive test count |
+| C++ | CMake build and CTest | CTest positive test count |
+
+C and C++ are separate language identifiers in configuration. JavaScript and TypeScript share the npm project plan; TypeScript type checking does not replace running tests.
+
+## Configure custom test commands
+
+For non-standard project layouts or test runners, create \`.polyguard.toml\` in the project root or pass one with \`--config\`.
+
+\`\`\`toml
+[project]
+languages = ["python"]
+
+[checks.python]
+commands = [
+  ["python3", "-m", "compileall", "-q", "src"],
+  ["python3", "-m", "pytest", "-q"],
+]
+test_patterns = ["tests/test_*.py", "tests/**/*.py"]
+success_patterns = ['(?m)^([0-9]+) passed']
+\`\`\`
+
+Configuration fields:
+- \`commands\`: non-empty argument arrays. Commands are launched without a shell.
+- \`test_patterns\`: at least one matching file must exist inside the project root.
+- \`success_patterns\`: optional regular expressions that extract a positive passing-test count from combined command output. If omitted, Polyguard uses the built-in pattern for that language.
+
+**Trust boundary:** a user-defined command or output regex is a project-owner assertion. A malicious or incorrect command can print a fake summary. Polyguard cannot independently prove what an arbitrary custom command did. For the strongest built-in verification, use the default language runner or a recognized test-runner adapter and its native report. Do not use \`echo\`, \`print\`, or a dummy process as a test command.
+
+The verifier rejects invalid regular expressions and test patterns that traverse outside the project root.
+
+## Test evidence and verdict rules
+
+A language check returns PASS only when:
+1. The project and required test suite are detected.
+2. Every required command completes successfully.
+3. The runner output contains a positive passing-test count, or a configured custom success pattern matches one.
+4. No command failure or timeout occurs.
+
+A zero-test run, an output with no recognized success summary, or a non-zero exit code returns FAIL. In JSON and detailed output, Polyguard includes the parsed test count and the evidence summary when available.
+
+## Integration tests
+
+The repository includes disposable real-project fixtures for toolchains available in the local environment. Run:
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+\`\`\`
+
+Integration fixtures are created in temporary directories and run through Polyguard's actual project discovery and command execution path. Missing local toolchains are skipped by local integration tests; CI jobs install their required toolchains explicitly.
+
+## AI coding-agent skill
+
+The repository includes \`SKILL.md\`, also shipped in the installed package. Agents should run:
+
+\`\`\`bash
+polyguard verify --path . --details
+\`\`\`
+
+Agents must not report successful verification unless the command exits 0 and returns PASS. They must not delete, skip, or weaken tests to manufacture a passing result.
+
+## Important limitations and security
+
+Polyguard is a test-execution gate, **not a formal proof of program correctness**. PASS means that the configured commands succeeded and a positive test-pass summary was recognized. It does not guarantee adequate test coverage, correct requirements, absence of defects, or trustworthy user-defined commands/patterns.
+
+The verifier executes project build scripts, package managers, and tests. Treat repositories and dependencies as untrusted. Run them in a disposable container or VM without secrets, privileged access, or sensitive host mounts. Polyguard does not itself provide operating-system isolation.
+
+Automatic language discovery is conservative. Custom frameworks can use explicit commands and success patterns. Full monorepo orchestration is not implemented yet: the current release does not discover every nested package or assign a separate working directory to each package. Run Polyguard separately from each package root until package-level configuration is added.
+
+## Development
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+python -m build
+python -m twine check dist/*
+\`\`\`
+
+## Publishing
+
+GitHub Actions builds the distributions and publishes with PyPI Trusted Publishing. Configure the PyPI publisher for:
+- Owner: \`Furox-Art\`
+- Repository: \`polyglot-code-guard\`
+- Workflow: \`publish.yml\`
+- Environment: \`pypi\`
+
+## License
+
+MIT

polyglot_code_guard-0.3.0/README.md

@@ -0,0 +1,147 @@
+# Polyguard
+
+**Fail-closed verification for AI-generated code across multiple programming languages.**
+
+Polyguard discovers supported project types, checks for a test suite, runs the relevant build/test commands, and returns a one-word verdict by default. A passing command exit code is not enough: Polyguard also requires a positive test-success summary from a recognized runner output format.
+
+## Install
+
+\`\`\`bash
+python -m pip install --upgrade polyglot-code-guard
+\`\`\`
+
+## Run
+
+From the target repository:
+
+\`\`\`bash
+polyguard verify
+\`\`\`
+
+Default output:
+
+\`\`\`text
+PASS
+\`\`\`
+
+or:
+
+\`\`\`text
+FAIL
+\`\`\`
+
+Diagnostics and automation:
+
+\`\`\`bash
+polyguard verify --details
+polyguard verify --json
+polyguard verify --path ./my-project --timeout 180
+polyguard verify --config ./ci/polyguard.toml
+polyguard --version
+\`\`\`
+
+Exit code is **0** for PASS and **1** for FAIL. Missing tests, missing toolchains, invalid configuration, a build/test failure, timeout, or missing positive test-execution evidence returns FAIL.
+
+## Built-in language support
+
+| Language | Default build/test plan | Positive execution evidence |
+| --- | --- | --- |
+| Python | \`compileall\`, then \`pytest -q\` | Pytest passed-test summary |
+| Rust | \`cargo test --all-targets\` | Cargo test-result summary |
+| Go | \`go test -json ./...\` | Passing test events in JSON stream |
+| JavaScript / TypeScript | \`npm test\`; TypeScript also runs \`tsc --noEmit\` when configured | Recognized runner pass summary |
+| Java | Maven test or Gradle test | Maven/Gradle test summary |
+| C# | \`dotnet test\` | .NET test-runner pass summary |
+| PHP | PHPUnit | PHPUnit success summary |
+| Ruby | RSpec, or Ruby's Minitest runner | RSpec/Minitest success summary |
+| Swift | \`swift test\` | Swift test-result summary |
+| C | CMake build and CTest | CTest positive test count |
+| C++ | CMake build and CTest | CTest positive test count |
+
+C and C++ are separate language identifiers in configuration. JavaScript and TypeScript share the npm project plan; TypeScript type checking does not replace running tests.
+
+## Configure custom test commands
+
+For non-standard project layouts or test runners, create \`.polyguard.toml\` in the project root or pass one with \`--config\`.
+
+\`\`\`toml
+[project]
+languages = ["python"]
+
+[checks.python]
+commands = [
+  ["python3", "-m", "compileall", "-q", "src"],
+  ["python3", "-m", "pytest", "-q"],
+]
+test_patterns = ["tests/test_*.py", "tests/**/*.py"]
+success_patterns = ['(?m)^([0-9]+) passed']
+\`\`\`
+
+Configuration fields:
+- \`commands\`: non-empty argument arrays. Commands are launched without a shell.
+- \`test_patterns\`: at least one matching file must exist inside the project root.
+- \`success_patterns\`: optional regular expressions that extract a positive passing-test count from combined command output. If omitted, Polyguard uses the built-in pattern for that language.
+
+**Trust boundary:** a user-defined command or output regex is a project-owner assertion. A malicious or incorrect command can print a fake summary. Polyguard cannot independently prove what an arbitrary custom command did. For the strongest built-in verification, use the default language runner or a recognized test-runner adapter and its native report. Do not use \`echo\`, \`print\`, or a dummy process as a test command.
+
+The verifier rejects invalid regular expressions and test patterns that traverse outside the project root.
+
+## Test evidence and verdict rules
+
+A language check returns PASS only when:
+1. The project and required test suite are detected.
+2. Every required command completes successfully.
+3. The runner output contains a positive passing-test count, or a configured custom success pattern matches one.
+4. No command failure or timeout occurs.
+
+A zero-test run, an output with no recognized success summary, or a non-zero exit code returns FAIL. In JSON and detailed output, Polyguard includes the parsed test count and the evidence summary when available.
+
+## Integration tests
+
+The repository includes disposable real-project fixtures for toolchains available in the local environment. Run:
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+\`\`\`
+
+Integration fixtures are created in temporary directories and run through Polyguard's actual project discovery and command execution path. Missing local toolchains are skipped by local integration tests; CI jobs install their required toolchains explicitly.
+
+## AI coding-agent skill
+
+The repository includes \`SKILL.md\`, also shipped in the installed package. Agents should run:
+
+\`\`\`bash
+polyguard verify --path . --details
+\`\`\`
+
+Agents must not report successful verification unless the command exits 0 and returns PASS. They must not delete, skip, or weaken tests to manufacture a passing result.
+
+## Important limitations and security
+
+Polyguard is a test-execution gate, **not a formal proof of program correctness**. PASS means that the configured commands succeeded and a positive test-pass summary was recognized. It does not guarantee adequate test coverage, correct requirements, absence of defects, or trustworthy user-defined commands/patterns.
+
+The verifier executes project build scripts, package managers, and tests. Treat repositories and dependencies as untrusted. Run them in a disposable container or VM without secrets, privileged access, or sensitive host mounts. Polyguard does not itself provide operating-system isolation.
+
+Automatic language discovery is conservative. Custom frameworks can use explicit commands and success patterns. Full monorepo orchestration is not implemented yet: the current release does not discover every nested package or assign a separate working directory to each package. Run Polyguard separately from each package root until package-level configuration is added.
+
+## Development
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+python -m build
+python -m twine check dist/*
+\`\`\`
+
+## Publishing
+
+GitHub Actions builds the distributions and publishes with PyPI Trusted Publishing. Configure the PyPI publisher for:
+- Owner: \`Furox-Art\`
+- Repository: \`polyglot-code-guard\`
+- Workflow: \`publish.yml\`
+- Environment: \`pypi\`
+
+## License
+
+MIT

{polyglot_code_guard-0.2.0 → polyglot_code_guard-0.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "polyglot-code-guard"
-version = "0.2.0"
+version = "0.3.0"
 description = "Fail-closed, multi-language test verification for AI-generated code."
 readme = "README.md"
 requires-python = ">=3.10"

polyglot_code_guard-0.3.0/src/polyglot_code_guard.egg-info/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.4
+Name: polyglot-code-guard
+Version: 0.3.0
+Summary: Fail-closed, multi-language test verification for AI-generated code.
+Author: Furox-Art
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/Furox-Art/polyglot-code-guard
+Project-URL: Repository, https://github.com/Furox-Art/polyglot-code-guard
+Project-URL: Issues, https://github.com/Furox-Art/polyglot-code-guard/issues
+Keywords: testing,code-verification,polyglot,ai-generated-code,quality-gate
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: tomli>=2; python_version < "3.11"
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == "test"
+Dynamic: license-file
+
+# Polyguard
+
+**Fail-closed verification for AI-generated code across multiple programming languages.**
+
+Polyguard discovers supported project types, checks for a test suite, runs the relevant build/test commands, and returns a one-word verdict by default. A passing command exit code is not enough: Polyguard also requires a positive test-success summary from a recognized runner output format.
+
+## Install
+
+\`\`\`bash
+python -m pip install --upgrade polyglot-code-guard
+\`\`\`
+
+## Run
+
+From the target repository:
+
+\`\`\`bash
+polyguard verify
+\`\`\`
+
+Default output:
+
+\`\`\`text
+PASS
+\`\`\`
+
+or:
+
+\`\`\`text
+FAIL
+\`\`\`
+
+Diagnostics and automation:
+
+\`\`\`bash
+polyguard verify --details
+polyguard verify --json
+polyguard verify --path ./my-project --timeout 180
+polyguard verify --config ./ci/polyguard.toml
+polyguard --version
+\`\`\`
+
+Exit code is **0** for PASS and **1** for FAIL. Missing tests, missing toolchains, invalid configuration, a build/test failure, timeout, or missing positive test-execution evidence returns FAIL.
+
+## Built-in language support
+
+| Language | Default build/test plan | Positive execution evidence |
+| --- | --- | --- |
+| Python | \`compileall\`, then \`pytest -q\` | Pytest passed-test summary |
+| Rust | \`cargo test --all-targets\` | Cargo test-result summary |
+| Go | \`go test -json ./...\` | Passing test events in JSON stream |
+| JavaScript / TypeScript | \`npm test\`; TypeScript also runs \`tsc --noEmit\` when configured | Recognized runner pass summary |
+| Java | Maven test or Gradle test | Maven/Gradle test summary |
+| C# | \`dotnet test\` | .NET test-runner pass summary |
+| PHP | PHPUnit | PHPUnit success summary |
+| Ruby | RSpec, or Ruby's Minitest runner | RSpec/Minitest success summary |
+| Swift | \`swift test\` | Swift test-result summary |
+| C | CMake build and CTest | CTest positive test count |
+| C++ | CMake build and CTest | CTest positive test count |
+
+C and C++ are separate language identifiers in configuration. JavaScript and TypeScript share the npm project plan; TypeScript type checking does not replace running tests.
+
+## Configure custom test commands
+
+For non-standard project layouts or test runners, create \`.polyguard.toml\` in the project root or pass one with \`--config\`.
+
+\`\`\`toml
+[project]
+languages = ["python"]
+
+[checks.python]
+commands = [
+  ["python3", "-m", "compileall", "-q", "src"],
+  ["python3", "-m", "pytest", "-q"],
+]
+test_patterns = ["tests/test_*.py", "tests/**/*.py"]
+success_patterns = ['(?m)^([0-9]+) passed']
+\`\`\`
+
+Configuration fields:
+- \`commands\`: non-empty argument arrays. Commands are launched without a shell.
+- \`test_patterns\`: at least one matching file must exist inside the project root.
+- \`success_patterns\`: optional regular expressions that extract a positive passing-test count from combined command output. If omitted, Polyguard uses the built-in pattern for that language.
+
+**Trust boundary:** a user-defined command or output regex is a project-owner assertion. A malicious or incorrect command can print a fake summary. Polyguard cannot independently prove what an arbitrary custom command did. For the strongest built-in verification, use the default language runner or a recognized test-runner adapter and its native report. Do not use \`echo\`, \`print\`, or a dummy process as a test command.
+
+The verifier rejects invalid regular expressions and test patterns that traverse outside the project root.
+
+## Test evidence and verdict rules
+
+A language check returns PASS only when:
+1. The project and required test suite are detected.
+2. Every required command completes successfully.
+3. The runner output contains a positive passing-test count, or a configured custom success pattern matches one.
+4. No command failure or timeout occurs.
+
+A zero-test run, an output with no recognized success summary, or a non-zero exit code returns FAIL. In JSON and detailed output, Polyguard includes the parsed test count and the evidence summary when available.
+
+## Integration tests
+
+The repository includes disposable real-project fixtures for toolchains available in the local environment. Run:
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+\`\`\`
+
+Integration fixtures are created in temporary directories and run through Polyguard's actual project discovery and command execution path. Missing local toolchains are skipped by local integration tests; CI jobs install their required toolchains explicitly.
+
+## AI coding-agent skill
+
+The repository includes \`SKILL.md\`, also shipped in the installed package. Agents should run:
+
+\`\`\`bash
+polyguard verify --path . --details
+\`\`\`
+
+Agents must not report successful verification unless the command exits 0 and returns PASS. They must not delete, skip, or weaken tests to manufacture a passing result.
+
+## Important limitations and security
+
+Polyguard is a test-execution gate, **not a formal proof of program correctness**. PASS means that the configured commands succeeded and a positive test-pass summary was recognized. It does not guarantee adequate test coverage, correct requirements, absence of defects, or trustworthy user-defined commands/patterns.
+
+The verifier executes project build scripts, package managers, and tests. Treat repositories and dependencies as untrusted. Run them in a disposable container or VM without secrets, privileged access, or sensitive host mounts. Polyguard does not itself provide operating-system isolation.
+
+Automatic language discovery is conservative. Custom frameworks can use explicit commands and success patterns. Full monorepo orchestration is not implemented yet: the current release does not discover every nested package or assign a separate working directory to each package. Run Polyguard separately from each package root until package-level configuration is added.
+
+## Development
+
+\`\`\`bash
+python -m pip install -e ".[test]"
+python -m pytest -q
+python -m build
+python -m twine check dist/*
+\`\`\`
+
+## Publishing
+
+GitHub Actions builds the distributions and publishes with PyPI Trusted Publishing. Configure the PyPI publisher for:
+- Owner: \`Furox-Art\`
+- Repository: \`polyglot-code-guard\`
+- Workflow: \`publish.yml\`
+- Environment: \`pypi\`
+
+## License
+
+MIT

polyglot_code_guard-0.3.0/src/polyguard/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: polyglot-code-verification
+description: Verify AI-generated code with actual project test runners and fail closed when tests do not execute or fail.
+---
+
+# Polyglot Code Verification
+
+Use this skill whenever code is generated, changed, refactored, or described as complete.
+
+## Required workflow
+
+1. Identify every language, build system, package root, and test framework touched by the change.
+2. Add requirement-based tests for normal behavior, edge cases, invalid inputs, error paths, and regressions.
+3. Run \`polyguard verify --path . --details\`.
+4. For a non-standard test runner, configure explicit commands, file patterns, and a success-summary parser in \`.polyguard.toml\`.
+5. Run the complete configured test suite. Do not omit a detected or required language.
+6. Require a positive passed-test count in recognized runner output. A successful command exit code or a test-looking filename alone is not sufficient.
+7. If a command fails, a toolchain is missing, tests cannot be found, the runner reports no passing tests, execution times out, or output evidence is missing, the verdict is FAIL.
+8. Fix the implementation or tests and rerun all checks. Never delete, skip, weaken, or rewrite a valid test merely to obtain PASS.
+9. Retain command output and the JSON report when inspectable evidence is requested.
+
+## Output contract
+
+- All required checks complete and positive test-pass evidence is present: PASS
+- Any failure or incomplete verification: FAIL
+
+The CLI exits 0 only for PASS and 1 for FAIL. Default output is exactly one word; use \`--details\` or \`--json\` for diagnostics.
+
+## Custom command trust
+
+A custom \`success_patterns\` entry is a trusted assertion by the repository owner about command output. It is not independent proof that the command executed real tests. Do not use a dummy command that prints a success-looking summary. Prefer built-in adapters and native test reports.
+
+## Scope
+
+Built-in support: Python, Rust, Go, JavaScript/TypeScript, Java, C#, PHP, Ruby, Swift, C, and C++ with CMake/CTest. Use explicit configuration for unconventional project layouts and custom runners. Full monorepo orchestration is not implemented; run Polyguard separately from each package root.
+
+## Security
+
+The verifier executes build tools, package managers, scripts, and tests from the target repository. Run untrusted code in a disposable container or isolated virtual machine without secrets, privileged access, or sensitive host mounts. Polyguard is not an operating-system sandbox.

{polyglot_code_guard-0.2.0 → polyglot_code_guard-0.3.0}/src/polyguard/__init__.py

@@ -1,3 +1,3 @@
 """Polyguard: fail-closed verification for multi-language projects."""
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"