Skip to content

Security: WhalerMike/uiao-impl

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.1.x

Reporting a Vulnerability

If you discover a security vulnerability, please do not open a public GitHub issue.

Instead, please report it via GitHub''s private vulnerability reporting feature: Report a Vulnerability

You can expect an initial response within 72 hours and a resolution timeline within 14 days for critical issues.

AI Agent Governance

This section defines the governance policy for AI coding agents (e.g., GitHub Copilot Coding Agent) operating in this repository.

Scope

These rules apply to all automated agents that read, generate, or modify files in this repository, including but not limited to GitHub Copilot, Dependabot, and any custom workflow bots.

Permitted Actions

  • Reading source files, templates, and test fixtures to implement or refactor library code.
  • Creating or updating files in src/, tests/, scripts/, adapters/, and orchestrator/ as part of the defined development workflow.
  • Opening pull requests that include only bug fixes, feature additions with tests, or dependency updates.
  • Running approved scripts listed in scripts/ with inputs validated against canon schemas from uiao-core.

Prohibited Actions

  • Committing secrets, credentials, API keys, or PII directly into any file.
  • Modifying the package version in pyproject.toml or src/uiao_impl/__init__.py without a human-reviewed pull request.
  • Disabling or bypassing branch protection rules, required status checks, or secret-scanning alerts.
  • Exfiltrating repository contents to unapproved external endpoints.
  • Self-modifying workflow files (.github/workflows/) without explicit human approval.
  • Declaring or defining canonical governance artifacts (YAMLs, schemas, rules) — those live in uiao-core and must not be duplicated here.

Secret Scanning

Secret scanning is enforced on all branches via GitHub''s native secret-scanning. Any detected secret triggers an automatic alert and blocks the affected pull request until the secret is rotated and the alert is resolved.

Audit Trail

Every action taken by an AI agent must be traceable via:

  1. A commit message following the [UIAO-IMPL] <verb>: <short description> convention.
  2. A linked pull request or workflow run in GitHub Actions.
  3. Retention of security audit artifacts for a minimum of 90 days.

Human-in-the-Loop Requirements

The following changes always require a human reviewer to approve before merging:

  • Changes to pyproject.toml (dependency pins, package metadata, entry points).
  • Changes to src/uiao_impl/__init__.py (version declaration).
  • Changes to .github/workflows/ (CI/CD pipeline configuration).
  • Changes to SECURITY.md or CLAUDE.md.
  • Any change that modifies GitHub Actions permissions or secrets.
  • Any change that alters the canon-path contract (--canon-path CLI flag semantics).

Compliance

This governance policy aligns with:

  • NIST SP 800-53 Rev 5 — SI-7 (Software, Firmware, and Information Integrity), AU-2 (Event Logging)
  • NIST SP 800-218 — Secure Software Development Framework (SSDF)
  • CISA Secure-by-Design Principles

There aren’t any published security advisories