feat(docs): Rewrite 'Why OpenTaint' messaging to align README, docs, and landing page#84
Merged
misonijnik merged 11 commits intomainfrom Apr 7, 2026
Merged
feat(docs): Rewrite 'Why OpenTaint' messaging to align README, docs, and landing page#84misonijnik merged 11 commits intomainfrom
misonijnik merged 11 commits intomainfrom
Conversation
Add problem-framing paragraph before feature bullets. Rewrite headers to be benefit-forward instead of mechanism-forward. Replace 'AI agent-ready' with 'Deterministic by design' to highlight the actual differentiator. Add quantification (100+ rules, 20+ vulnerability classes) and name the rule format (Semgrep-compatible YAML).
Rewrite intro paragraph: hook (AI outpaces security tooling) → evidence (hidden vulns in structural data flows) → human review gap → tool failures (pattern matching engines, LLM agents, enterprise analyzers) → thesis (formal analysis underneath). Restructure bullets to match plan's Primary/Secondary/Tertiary: - Finds what pattern matching engines miss (detection depth) - One finding becomes total coverage (AI flywheel + determinism) - Open source, batteries included (competitor contrast) Move detailed explanations to docs/README.md, keep README compact.
Rewrite sub-hero line: find → enact → scale pipeline with parallel clause structure. Split intro wall into three paragraphs for breathing room, thesis lands as standalone one-liner. Fix wording: 'coverage' → 'they caught everything', 'vendor lock-in' → 'your rules live in your repo', trim documentation filler.
Replace 'including the deep analysis' and 'your rules live in your repo' with 'no gates on writing your own rules' — the real lock-in is that closed tools prevent rule authoring, not that they take rules.
…ging - Fix 'uncoveted' → 'uncovered' and 'allow to enact' → 'let you codify' - Add paragraph break in docs/README.md intro for readability - Standardize on 'the engine' as subject across both READMEs
misonijnik
force-pushed
the
misonijnik/update-readme
branch
from
6ab25f4 to
f8f2713
Compare
…-dna - Fix Semgrep FAQ to distinguish OSS (pattern matching) from Pro (paid taint) - Add cost argument to AI agent FAQ answer - Replace enterprise-grade with formal inter-procedural in CodeQL FAQ - Strengthen CodeQL FAQ with QL barrier and AI writability angle - Fix stale tagline in What is OpenTaint FAQ answer - Remove redundant "framework ecosystem" wording - Fix what -> where in README sub-hero tagline
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
1 participant
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.
No description provided.