Skip to content

v0.4.0 — security hardening + red/blue-team audit

Choose a tag to compare

View all tags
@cschweda cschweda released this 17 Apr 15:10
v0.4.0
f0193f7

Superseded by v0.4.1, which fixes a pre-existing YAML frontmatter parse error and publishes the real install checksum. Prefer v0.4.1 for new installs.

Security-focused release. Remediates the ten red/blue-team findings in SECURITY_REVIEW.md; adds a new ## Security section to the README.

Security

  • Red-team / blue-team audit published as SECURITY_REVIEW.md. Full threat model, input-surface inventory, ten red-team findings with severities and reproductions, blue-team mitigations, documentation-drift notes, recommendations, and per-finding remediation status.
  • Read-scope policy in refine.md Step 1. The refiner refuses to open files outside the current working directory or matching a secret-file denylist (.env*, *.pem, *.key, id_rsa*, id_ed25519*, id_ecdsa*, .aws/**, .ssh/**, .gnupg/**, .netrc, .npmrc, .pypirc). Closes RT-03, RT-04.
  • Data-not-instructions framing in Step 1 and Step 1a. Rough-prompt text, file contents, and multimodal attachment transcripts are inputs to summarize, not instructions to execute; override attempts are surfaced in Assumptions to confirm. Closes RT-01, RT-06.
  • Immutable approval gate in Step 4. The Execute this refined prompt? (yes / edit / cancel) question is fixed verbatim; reworded or alternate answers are rejected. Closes RT-02.
  • Trust-sensitive label on the "Project conventions to apply" block, mirrored as a Customize trust note in the README. Closes RT-07.
  • Mode-token normalization (strip surrounding whitespace/quotes, apply NFKC). Closes RT-08.

Changed

  • Install pinned to a release tag and checksummed. Install command now uses the v0.4.0 tag (not main) and shows a shasum -a 256 -c verification step. Closes RT-05.
  • "No API calls" wording softened in the How-it-works section. Closes RT-09.
  • Project-scoped-install warning surfaced in the main Install section. Closes RT-10.

Added

  • New ## Security section in README.md (with a matching TOC entry) summarizing the inputs the refiner reads, the defenses baked into the template, what sits outside scope, and linking to SECURITY_REVIEW.md.

See CHANGELOG.md for the full version history.

Assets 2
Loading