Add opensource pipeline agents (forker, sanitizer, packager)#157
Closed
herakles-dev wants to merge 4 commits intoVoltAgent:mainfrom
Closed
Add opensource pipeline agents (forker, sanitizer, packager)#157herakles-dev wants to merge 4 commits intoVoltAgent:mainfrom
herakles-dev wants to merge 4 commits intoVoltAgent:mainfrom
Conversation
Three agents forming a complete open-source release pipeline: - opensource-forker: strips secrets, replaces internal refs, generates .env.example - opensource-sanitizer: independent PASS/FAIL audit with 30+ secret patterns - opensource-packager: generates CLAUDE.md, setup.sh, README, LICENSE, CONTRIBUTING All three agents added to categories/04-quality-security/ with descriptions updated in both the category README and main README in alphabetical order. Pipeline source: https://github.com/herakles-dev/opensource-pipeline
…1/P2 review fixes) - forker: rsync now excludes .env* (variants), .claude/, .secrets/, secrets/ - forker/sanitizer: AWS regex covers aws_secret alias + case-insensitive, min 20 chars - forker/sanitizer: JWT pattern requires full 3-segment structure - forker/sanitizer: GitHub tokens cover all token types (gh[pousr]_), min length 36+ - forker: generic env pattern increases min length 8→16, adds non-secret lookaheads - sanitizer: high-entropy WARNING separated from CRITICAL scan categories - sanitizer: internal path detection broadened to macOS /Users/ and Windows C:\Users\ - sanitizer: read-only rule clarified to "never modify source files — only generate reports"
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Addresses 28 review comments plus 5 previously-unresolved findings: - Nuanced *.pem/*.key handling (test certs vs real private keys) - Explicit guard against real secret values in .env.example - RFC1918 172.16-31.x.x range in forker replacement table - Windows/macOS path detection with multi-char usernames - Sanitizer validates .env.example contains only placeholders - Packager uses indented template blocks for nested fenced code Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
|
Thanks for the submission. However, the project looks quite new at the moment. Please feel free to open a new PR once it has matured a bit more. In the meantime, we recommend reviewing the contribution guide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds three agents that form a complete open-source release pipeline to the Quality & Security category:
opensource-forker — Stage 1: Copies a private project to a staging directory, strips 30+ secret patterns (API keys, DB credentials, private keys, tokens, OAuth secrets), replaces internal references (domains, home paths, private IPs), and generates
.env.examplefrom all extracted configuration. Produces aFORK_REPORT.mddocumenting every change.opensource-sanitizer — Stage 2: Independent read-only auditor that verifies the fork is safe for release. Scans across 6 categories (secrets, PII, internal references, dangerous files, config completeness, git history) and produces a
SANITIZATION_REPORT.mdwith a PASS / FAIL / PASS WITH WARNINGS verdict. Never trusts the forker's work.opensource-packager — Stage 3: Generates professional open-source packaging after the sanitizer issues a PASS. Produces
CLAUDE.md(Claude Code context file),setup.sh(one-command bootstrap with prerequisite checks), enhancedREADME.md(with "Using with Claude Code" section),LICENSE,CONTRIBUTING.md, and optional GitHub issue templates.Pipeline:
opensource-forker→opensource-sanitizer→opensource-packagerFull pipeline source and orchestration skill: https://github.com/herakles-dev/opensource-pipeline
Changes
categories/04-quality-security/opensource-forker.md— new agentcategories/04-quality-security/opensource-sanitizer.md— new agentcategories/04-quality-security/opensource-packager.md— new agentcategories/04-quality-security/README.md— added agent descriptions, updated Quick Selection Guide and Common PatternsREADME.md— added three entries in alphabetical order within the Quality & Security sectionTest plan
name,description,tools,model)categories/04-quality-security/matching the existing naming conventionREADME.mdentries are in alphabetical order within the category sectionREADME.mdincludes agent descriptions with Use when: guidance🤖 Generated with Claude Code