Skip to content

chore: add security policy and normalize license placement - #84

Open
PenguinzTech wants to merge 1 commit into
v2.1.xfrom
chore/security-policy
Open

chore: add security policy and normalize license placement#84
PenguinzTech wants to merge 1 commit into
v2.1.xfrom
chore/security-policy

Conversation

@PenguinzTech

Copy link
Copy Markdown
Contributor

Adds a house-standard SECURITY.md to Squawk.

What's in it

  • Private disclosure to security@penguintech.io — no public issues for vulns
  • 48h acknowledgement / 5-business-day triage targets
  • Safe-harbour terms for good-faith researchers
  • Supported-version policy (current line, N-1 for high/critical)
  • The security defaults this codebase ships with: multi-tenant isolation at the query layer, OIDC scope-based authz, short-lived rotating JWTs, SPIFFE-ready service identity, encryption in transit and at rest, rootless containers, default-deny networking, pinned dependencies, enforced 90% coverage
  • Compliance framed as designed to support, with an explicit statement that this is not a certification claim

License: moved to a root LICENSE.md using our AGPL-3.0 text with the standard preamble (no commercial repacking; internal corporate and individual non-commercial use permitted; GPL-2.0 exception for contributors' employers). GitHub only detects a license at the repository root, so a copy under docs/ left this repo showing as unlicensed.

🤖 Generated with Claude Code

Adds a house-standard SECURITY.md: private disclosure via
security@penguintech.io, acknowledgement and triage targets, safe-harbour
terms for good-faith researchers, supported-version policy, and the security
defaults this codebase actually ships with.

Compliance frameworks are described as architectural alignment, explicitly
not as certification claims.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@PenguinzTech PenguinzTech self-assigned this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant