Repository navigation
Releases
Releases · Guzman0/DappSentinel
DappSentinel v1.1.0
What's new in v1.1.0
Security
- The action now keeps only DappSentinel's report, with keys masked. Kane's raw evidence (network logs, storage snapshots) is no longer uploaded by default, because it can hold the very secrets the checks look for.
- If you do want the raw evidence, set
keep-evidence: true. It is kept for 3 days. - New SECURITY.md explains what is collected, kept and uploaded.
More reliable results
- If Kane couldn't load the page (for example, a bot challenge), the network checks are marked inconclusive instead of passing or failing the site.
- A flaky recording run no longer marks a fixed site as failing.
- The contract address and chain ID are each checked with one direct assertion.
- The report quotes the line of Kane's summary that says what it actually saw.
Maintenance
- The action's building blocks move to their Node.js 24 versions, so the Node 20 deprecation warnings are gone.
Proven with a mutation test
The fixed demo plus 7 copies, each with one new mistake: 8 of 8 judged correctly, on two separate runs. Full record: evidence/mutation-test/
Use it
uses: Guzman0/DappSentinel@v1.1.0
DappSentinel v1
First release of DappSentinel as a GitHub Action.
Kane CLI checks your dApp in a real browser for mistakes you can't see on screen: leaked RPC API keys, testnet endpoints in a mainnet build, untrusted scripts and private keys in browser storage. The step fails while any check fails.
- uses: Guzman0/DappSentinel@v1
with:
url: https://staging.yourdapp.xyz
lt-username: ${{ secrets.LT_USERNAME }}
lt-access-key: ${{ secrets.LT_ACCESS_KEY }}
See the README for checking a built folder (site-dir), your own config, and real-world runs on Lido, Aave and CoW Swap.