Docs & Rules

jbangdev/jbangGitHubLast refreshed Oct 2, 2026

This is a public, read-only report. Striff reads this repository's docs, turns each sentence that makes a claim about the code into a rule, and checks the rule against the code on the default branch. How this works

2 names in these docs no longer match the code.

maincae3ad7listed 21h ago

Is this yours? Install to manage it

Once installed, Striff checks every pull request.

3
1 stale3
1 staleSkipped
25 docs, listed Oct 2
jbangdev/jbangOpen repository

Names these docs write that the code no longer has2

Each sentence below names a type the default branch doesn't declare, or declares somewhere else. Edit the doc so it matches the code, or bring the type back.

  • Moveddev.jbang.cli.ExitException
    Error handling: throw dev.jbang.cli.ExitException for controlled exits; let picocli report parameter issues.

    The code declares it in dev.jbang, at src/main/java/dev/jbang/ExitException.java, not in dev.jbang.cli.

    View on GitHub

  • Gonedev.jbang.VersionProvider
    The dev.jbang.VersionProvider class will show a compile error in IDE's but ignore that, the BUILDCONFIG class gets generated during the Gradle build.

    dev.jbang declares nothing by this name.

    View on GitHub

jbangdev/jbang — documented rules

3 of 3 rules, printed October 3, 2026.

The sentence in your docs
Read Oct 2
Logging/output: use dev.jbang.util.Util helpers (e.g., infoMsg, verboseMsg).
Util has infoMsg
Holds
Read Oct 2
Logging/output: use dev.jbang.util.Util helpers (e.g., infoMsg, verboseMsg).
Util has verboseMsg
Holds
Read Oct 2
Authentication/credential chain: most-specific source wins. Order: URL userinfo → .netrc exact host → GITHUB_TOKEN/GITLAB_TOKEN → .netrc default → JBANG_AUTH_BASIC_*. For Maven repos, settings.xml <server> entries override all of the above when the server <id> matches. Shared logic lives in NetUtil.getCredentialsForHost(); don't duplicate the chain — call the shared method.
NetUtil has a getCredentialsForHost method
Holds
3 rules from 1 doc

See these where the change is. The browser extension puts a pull request's doc findings, and a diagram of what it changed, on the GitHub page itself, so the code and what your docs say about it are side by side.