Skip to content

fix: Enhance builtin rules resolution and update README documentation - #1

Merged
misonijnik merged 3 commits into
mainfrom
feat/builtin-rules-engine-discovery
Jun 16, 2026
Merged

fix: Enhance builtin rules resolution and update README documentation#1
misonijnik merged 3 commits into
mainfrom
feat/builtin-rules-engine-discovery

Conversation

@misonijnik

Copy link
Copy Markdown
Member

No description provided.

The npm/npx-installed viewer ships only the viewer, not the engine's
ruleset, so the old `../lib/rules`-next-to-the-CLI default never
resolved
for npm users and the CLI hard-failed.

Resolve `--builtin-rules` in priority order: explicit flag, then
`../lib/rules` next to the `opentaint` engine binary found on PATH (when
that dir exists), then the CLI-relative path (the bundled-with-engine
layout). This makes the common `--sarif`-only invocation work whenever
the engine is installed.

Also document npx vs. global-install CLI usage in the README and update
the `--help`/options-table defaults to match.
Restructure the README to match the seqra/opentaint style: centered logo,
tagline, badges, and demo screenshot up front; a short bold-bulleted "Why";
and a tight Quick Start.

Lead every user-facing flow with npx / the opentaint-viewer CLI (full
commands, no ellipses); the demo now scans seqra/java-spring-demo and views
it via npx instead of `npm run dev`. Describe taint in plain language —
"untrusted input" and "dangerous call" rather than source/sink. Tuck the
depth (full CLI options table, the legacy `npm run gen` build, and dev
scripts/stack) into <details> so nothing accurate is lost.
@misonijnik
misonijnik merged commit a9bd0d3 into main Jun 16, 2026
1 check passed
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