featkpr maps your web app and tests its permissions as the wrong user.
It reads the code, opens every screen and writes the tests itself. Here it is on BookStack, an open-source wiki we don't own.
- code read 343routes
- features named 307features
- screens crawled 167screens
- paths drafted 163paths
- tests run 304pass
- wrong-user check 269refused to the wrong user

Runs, in featkpr: every test, what it sent, what came back Each test runs twice: once with permission, once without.
- sign in
- open the shelf
- send the new book
as an Editorallowed to create bookspassed302, on to the shelf
as a readercan read, can't createrefused, as it should besent back to the home page
269 of 304 BookStack tests refused to the wrong user · 35 unchecked: no user without that permission exists to try them as yet
For an app that has grown past what anyone can list.
featkpr names what it does, drafts how people use it and proves the tests, so a change can't quietly open a door. What it does for your app →
The library
one product through all six steps, the next ones on their way
BookStackopen-source wiki 307 features in 12 modules · 163 paths to 69 goals · 304 tests pass, 269 refused to the wrong user · 605 of 2,372 missed in the missed-items check
Shlinkself-hosted URL shortener 28 routes read · 20 features named · the crawl and tests need a reader for its stack, which comes next
featkpr itselfthis product, on its own code dogfooding stage 1 built: 26 of its own screens entered as planned rows · reading its own merge requests, crawling and testing itself are planned
Next on the route
the whole plan is on the roadmap
A crawl that edits and deletes what it madereleased as a draft after approval
The goal ledgera goal's identity and 3 kinds of event
Effects in every runWeek 1 · from 5 Oct
Release flow and a Kargo planWeek 2 · from 12 Oct
See it on BookStack, privately
A live walkthrough first, then read-only access once invites exist.