Floorplan 0.10.02026-11-15
- One unusual letter no longer blanks the map: to list the page's own scripts in its Content-Security-Policy, the build reads a lower-cased copy of the page, and a few letters get longer when lower-cased (the Turkish "İ" becomes two characters). One of them anywhere before the scripts, in a comment the scan picked up, a file name or a description, moved every later script by one character in that copy, so their fingerprints were wrong, the browser blocked them and the map drew nothing. Only A to Z are lower-cased now, the way the browser reads tag names, so the copy always lines up with the page. Fixed by @OfficialCodeVoyage in #118.
- Fastify routes written as objects are found: a Fastify server that declares its endpoints as app.route({ method: 'POST', url: '/api/orders', handler }) had none of them on the map. They now count on any router the file makes (const api = Fastify()), with one endpoint per method when method is a list, and a preHandler, onRequest or preValidation check on the route protects only that route. A key inside the route's schema, and a method or url that isn't written out, don't make an endpoint. Fixed by @Bl0ck154 in #34.
- NestJS endpoints are on the map: a NestJS server used to show no endpoints at all, so its requests from the website weren't connected and Health couldn't say which endpoints anyone can call. Endpoints now come from @Controller('prefix') (or @Controller({ path })) and the @Get, @Post, @Put, @Patch, @Delete, @All, @Options and @Head decorators on its methods, each with its handler, in files that import @nestjs/common. A file with several controllers, or a controller followed by another class, keeps each endpoint under its own controller and named after its own method. Health reads @UseGuards(...) on a method or its class, a sign-in guard for the whole app ({ provide: APP_GUARD, useClass: AuthGuard } in a module, or app.useGlobalGuards(new JwtAuthGuard()) in main.ts), and the @Public()-style decorators that open a route past it (a public route that checks a token or signature itself still counts as checked). An app-wide guard protects the Nest controllers only, not an Express or Next.js server in the same repo, and rate-limit and quota guards, or one whose name doesn't say what it checks (MaintenanceGuard), don't count as sign-in checks. A global prefix set at run time (app.setGlobalPrefix) isn't seen yet. Fixed by @stefantalos in #111, with the several-controllers fix and sample from @BestShuffle in #82.
- Endpoints listed as data are found: some servers keep their endpoints in a list a dispatcher reads, like [{ method: "GET", path: "/api/items", handle: listItems }], where the path can be a regular expression (/^\/api\/items\/([^/]+)$/ is /api/items/:p1, and (?:items|products) gives one endpoint for each word), and Bun servers declare theirs in Bun.serve({ routes }). These had no endpoints on the map. Each one is now an endpoint named after its handler, and the website's requests are linked to it. A list of the requests a website makes ({ method, path, action: 'createOrder' }, or resolve and fetch functions) isn't taken for routes: action, resolve and fetch count only in a file that serves or next to entries with a handle, and the value must be a function. A pattern that can't be turned into a clear path is dropped rather than made to match everything. As with route tables keyed by method and path, Health doesn't judge their sign-in, which happens in the dispatcher. Fixed by @maxschuetz06 in #29.
- Angular routing files are no longer endpoints: under src/app/, a file whose name merely ends in route.ts (Angular's orders.route.ts) was read as a Next.js route handler, so it showed up as a GET endpoint and Health reported a whole Angular app's endpoints as open to anyone. Only a file named exactly route.ts is a Next.js route handler now. Fixed by @BestShuffle in #84.
- FastAPI routers with a check that takes arguments: a router like APIRouter(dependencies=[Depends(require_workspace("tours"))]), where a check's factory is called with arguments, was read only up to its first ), so its sign-in check was missed and all its routes were reported as open. The whole APIRouter(...) is now read, and a check named just authenticate or authorize counts. A check that only appears in a comment or a string inside it still protects nothing. Fixed by @spacecampkatie in #73.
- Requests through an app's own helpers are found: calls like apiGet('/tasks'), ` apiSend('PATCH', /tasks/${id}, body) or httpPost('/orders') are now web requests, with the method taken from the helper's name or its first argument. A phone app that made all its calls this way showed almost none. Fixed by @Basel-Alsemsam in #105.
- A client's base address wins over a closer-looking match: when a client's other calls all go under one base (its base URL holds /api/v2), an address like /tasks/${id} now reaches /api/v2/tasks/:id rather than a website page at /tasks/:id, even when both live in the same server file. A base is only learned from calls that every equally good match agrees on, so one ambiguous call can't teach the wrong one, and a base one app teaches is shared only with that app's own files (the folder with its package.json, or its repo), never with another app beside it. Fixed by @Basel-Alsemsam in #105.
- Requests built by a service method: an Angular service (or any class) that builds its addresses in a method, like this.http.post(this.url(id, '/ship'), {}) with url() returning a template string, now has those requests on the map, including methods that build on another one (itemUrl() calling url()). Before, they were missed or matched to the wrong endpoint from their last piece alone (/ship). Fixed by @BestShuffle in #83.
- Requests whose address is on the next line: this.http.patch<Order>( with the address on the line below now counts, with its method. Before, such a request was only found when its address happened to contain a word like api or base. Fixed by @BestShuffle in #83.
- Swift apps get their connections: Swift files showed no links at all, because a Swift import names a module rather than a file, and files of one module use each other's code without importing anything. Floorplan now reads every Package.swift to find each target's folder (its path:, or Sources/<name> and Tests/<name>), and links a file to the files declaring the types, type aliases, functions and values it uses, in its own module and in the modules it imports (including @testable import). An Xcode app with no package counts as one module, so its folders link to each other too. Nested and private declarations are left out, so common names like Kind or State don't link unrelated files, a name the file's own module declares wins over the same name in a module it imports, only tests link to test helpers, and a module the file imports but uses nothing visible from (only its extensions, say) gets no link rather than one picked at random. Apple's frameworks are left off the map, other packages (like Sparkle) show up as outside packages, and classes, structs, enums, protocols and actors are listed on each file's card, protocols and actors with the type icon. Contributed by @JohannDesobry in #79.
- Shopify themes are mapped: a theme's Liquid files weren't read at all, so its map had almost nothing on it. Now a folder with a layout/theme.liquid is read as a theme, and its files are linked the way Shopify loads them, by name: {% render %} to snippets, {% section %} and {% sections %} to sections and section groups, {% contentfor 'block' %} to theme blocks and asseturl` to assets. JSON templates and section groups use the sections and theme blocks they list, including Liquid typed into custom-code settings. Apps added as app blocks or embeds show up as outside pack
Floorplan 0.9.02026-11-15
- Flask login checks are recognised: routes protected by @loginrequired, @loginrequiredjson or @loggedinrequired were reported as open, because names starting with "log" were taken for logging decorators. Logging decorators such as @logcall still do not count as login checks, and a login decorator placed above the route remains a warning. Reported by @SmmSrg in #123, fixed by @daniyyell-dev in #125.
- FastAPI apps protected by one HTTP middleware: an @app.middleware("http") function that turns callers away (a 401 or 403 response, or HTTPException) now counts as the app's login check, so its endpoints are no longer reported as open to anyone. It works the same way Flask's @app.before_request already does. A middleware that only adds headers, measures time or reads a 401 from the response still protects nothing, whatever its name, and neither protects a JavaScript server in the same repo. Reported by @ahmedjanwar in #86 and fixed by them in #87.
- FastAPI checks named validate…: a dependency like Depends(validatejwt) or Depends(validateapikey) now counts as a login check. One that validates a request's shape, like @validate or Depends(validate_payload), still doesn't. Reported by @doramirdor in #112.
- FastAPI checks judged by what they do, not only their name: a route was reported as open when its check was the result of a factory (editor = requirerole("editor"), then Depends(editor), on the route or on the whole APIRouter), a dependency with an ordinary name that turns callers away with a 401 or 403 (Depends(currentvehicle), or a class whose call does), a Depends() kept in a variable (api = Depends(requirekey), then dependencies=[api] or : None = api), or a list kept in a constant (dependencies=WRITE). These now count. A dependency that checks nothing about the caller, like a page number or a lookup that answers 404, still protects nothing however it's passed. Reported by @RoelfA in #117 and @SomeRandomChad in #102.
- Imports stay linked when TypeScript settings come from several files: local arrays in tsconfig.json's extends now preserve inherited path aliases. Later configurations and the project's own settings take precedence, and relative paths keep the correct starting directory. Reported by @daniyyell-dev in #126, fixed by @daniyyell-dev in #127.
- Imports through package.json "imports" are linked: projects that import with Node subpath imports, like import { money } from '#lib/money' mapped by "imports": { "#": "./src/" }, had almost no links between their own files, so the map showed parts that seemed unconnected and Health listed most files as unused. Floorplan now follows the imports field of the nearest package.json the way Node does: an exact key first, then the most specific * key, trying each target and condition in turn (types last, since Node never picks it). tsconfig paths still apply when package.json has no match. Reported by @joelbeedle in #69, fixed by @joelbeedle in #68.
- Python imports between Django apps are linked: in a project with its apps in a package (apps/orders/, apps/core/), from apps.orders.models import Order was linked to the importing app's own apps.py, so the map had no links between apps and Health listed much-used files as unused. Floorplan now looks for the whole module in every folder an import can start from before settling for part of it. Reported by @m1fril in #99.
- Kotlin and Java files are linked to what they use: an import of a class, function, value or type alias that isn't named after its file (Kotlin files often hold several) was listed as an outside Maven package, often the app's own (com.example.app), and code a file uses from its own package, which needs no import, wasn't linked at all, so the map had few links between Kotlin files and descriptions said files were unused. Floorplan now knows every top-level declaration in a file, links a file to the files of its own package (and of a .* import) whose names it uses outside comments and strings, and never lists one of the project's own packages as an outside package. Private declarations, and test helpers used from outside the tests, aren't linked. Reported by @RoelfA in #115.
- Fewer false "secret key" alarms in Health: a variable handed along (MYSQLPWD="$DBPASSWORD" in a shell script, "$password" in PHP, %DBPASSWORD% on Windows), a path to one of the project's own files under a password-ish key ('confirmpassword' => 'resources/js/pages/auth/confirm-password.tsx'), and a ULID record id under a plain …Token name are no longer reported as secrets written into the code. Access, auth and secret tokens are still checked whatever their value looks like. Fixed by @Basel-Alsemsam in #104, which also fixes #116 (reported by @BechtelCanDoIt).
- More values that only look like secrets are left alone:
- variables in more spellings: $(dbPassword) in Azure Pipelines and Makefiles, #{password} in Ruby, a few joined together ("$DBUSER:$DBPASSWORD"), and psql variables in database set-up scripts (-v apppassword="$APPPASSWORD", then PASSWORD :'app_password'). Prompted by reports from @jeanlima17-cmd in #110 and @auroraferraz in #107 and #108;
- publishable keys, which services make to be put in web pages: pk… (Stripe, Clerk and others), Supabase's sbpublishable… and PostHog's phc…. A sk… key is still flagged, and so is a password that happens to start with pk. Reported by @notrdd in #119;
- the two answers of a choice, like mode === 'signup' ? 'new-password' : 'current-password', and the browser's autofill words (new-password, one-time-code). Reported by @adlewis82 in #93;
- made-up keys with a run of the alphabet or the digits in them (ghp_abcdefghij…0123456789…), even in a well-known format. A random-looking key is still flagged, in test files too. Reported by @lexerio-seth in #101.
- Fewer files wrongly called unused: Expo Router finds every file in an app's app/ folder by its place, so in an app that uses expo-router those screens no longer look unused (a leftover file in a Next.js app/ folder, or anywhere else, still does). And a file with dots in its name, like users.service.ts, now counts as used when another file names it ('./users/users.service'), as users.ts already did; before, the dot hid the name, so NestJS services and controllers reached through an import the map couldn't follow looked unused. Reported by @axelmorand-afk in #88 and #89, with the dotted-name cause found by @xunguangzlj-cloud in #100.
- Asking a question on the map no longer fails with “Prompt is too long”: two things could fill Claude Code’s context before it got to the question. On a computer with many MCP servers set up (connectors and plugins), each question loaded every one of their tool descriptions, though answers never use them; now questions run with no MCP servers at all, which also makes each one much cheaper. And Claude Code could open the map’s own generated floorplan/index.html (about 2 MB on one line); it’s now told not to read that file or the map’s other generated files. Codex has no switch that turns off only its MCP servers, so it still loads them. Reported by @Kadreev in #66, with the second fix by @psingh-valorx in #120.
- JSON files saved on Windows work: Windows PowerShell's Set-Content and Out-File, and some editors, start a file with an invisible byte order mark, and Floorplan stopped with architecture.json is not valid JSON: Unexpected token. Every file you or an agent write for Floorplan (architecture.json, descriptions/, recent-work.json, plan.json, saved flows and Health dismissals) now reads the same with one. The guides also say that their commands are written for a POSIX shell, with the PowerShell way where it differs. Reported by @fjjjuv in #95, with a first version of the fix by @1oridevs in #97.
- **The m
Floorplan 0.6.32026-11-02
- Endpoints in route tables (#54, from @Yahhi): servers without a framework often keep their endpoints in a lookup a dispatcher reads, keyed by method and path, like { "GET /api/orders": listOrders } in JavaScript or a Python dict of handlers behind a cloud function. Floorplan found no endpoints in these apps, so the website's requests weren't linked to the server. Now each key is an endpoint, named after its handler (a function, an inline function that calls one, or a wrapped one like requireAuth(createOrder)). Tables of other things keyed the same way, like access levels or notes, are left alone. Health doesn't judge sign-in on these endpoints, because the dispatcher or the handler checks it where Floorplan can't see.
- Fastify endpoints get their full address (#30, from @secatech): a plugin mounted with app.register(plugin, { prefix: '/api/tickets' }) now puts its endpoints under that prefix, including plugins registered inside other plugins and ones loaded with import() or require(). Before, every plugin's endpoints sat at the root (GET /, GET /:id), so the website's requests were often matched to the wrong part of the server.
- Django endpoints get their full address: an app's urls.py included by the project (path("api/orders/", include("orders.urls"))) now puts its endpoints under that prefix, as /api/orders/<int:pk> rather than /<int:pk>, so the website's requests link to them. The include line itself is no longer listed as an endpoint, and the project's urls.py links to the app's. Fixed by @rudycelekli (#64).
- Code after a / inside a string is read again: a string such as '/api/' (as in Hono's app.use('/api/*', cors())) was taken for the start of a comment, so every endpoint, import and web request from there to the next comment's end was missing from the map. Fixed by @rudycelekli (#61).
- Skill installation: quote the YAML description so npx skills add can read it. Fixed by @Bl0ck154 (#25), and @Mason-Little sent the same fix.
- Blueprints in Codex: the build report now says a blueprint is "planned, not built yet" in Codex too. Fixed by @owlahikit.
Floorplan 0.6.22026-11-02
- Far fewer false alarms in Health (thanks to @samuelpullen15-droid, who reported 13 of them from one site with the new Not a problem button):
- Feeds and files meant for everyone: reading rss.xml, atom.xml, llms.txt, ads.txt and similar no longer counts as an open endpoint.
- Addresses you publish yourself: an endpoint listed in your llms.txt, or allowed in your robots.txt, is public on purpose. A catch-all route counts when something under it is listed, and a blocked or merely nearby address doesn't.
- Responses marked for everyone: a Cache-Control: public response is public on purpose, including when a helper it imports sets the header. So is a Next.js route with force-static or revalidate.
- Nothing private to give: a Next.js GET that reads no database, session, cookie or server secret, directly or through what it imports, is no longer reported. A rate limiter's Redis doesn't count, an import Floorplan can't follow does, and so does reading files on a route whose address the caller chooses.
- Payload CMS: the API routes Payload generates apply its own access rules, so they no longer read as "anyone could change data".
- A "POST only" reply: a handler that only answers 405 isn't an open endpoint or a way to send fake events.
- Webhooks locked with a shared secret: comparing against a secret from the environment, timingSafeEqual, and helpers like isAuthorized() or verifyWebhookSecret() now count as checks on Next.js routes.
- A browser tracker's site token: a token handed to a tracker's <script> tag is one every visitor already has. Names like ACCESSTOKEN or AUTHTOKEN, and real key formats, are still reported.
- Files a tool opens by name: a file whose comment says a tool reads it, or that it's generated, no longer looks unused.
- Endpoints that change data are still always checked, and "Not a problem" is still there for anything Health can't work out.
- FastAPI checks Health missed (#7), fixed by @Bl0ck154: dependencies named like metrics_guard, a token in a Header parameter when the handler rejects a bad one, a Twilio-style signature check inside a helper, and /readyz and /livez as public health checks.
- Health reads each Express route's own checks: a sign-in check in front of a handler defined elsewhere (router.post('/books', requireAuth, createBook)) was missed, so the endpoint was reported as open to anyone. The other way round, a route could borrow the check of the route below it, and a handler whose name sounds like a check (updateUser) was taken for one, so some open endpoints weren't reported. Fixed by @rudycelekli.
Floorplan 0.6.12026-11-01
- Fewer false alarms in Health (thanks to the user who reported these):
- A password hash isn't the password: bcrypt, argon2 and similar hashes are no longer reported as passwords, and neither is anything under a name like ADMINPASSWORDHASH, including browser variables such as VITEADMINPASSWORDHASH. The secret that makes a hash (HASHSECRET) is still flagged, and so is a real key format under any name.
- An encrypted backup isn't an exposed one: encrypted values in a .env file are left alone (dotenvx, sops, Ansible Vault, AWS KMS, HashiCorp Vault, age, PGP, OpenSSL and Fernet), and so are passphrase-protected private keys. A value left unencrypted next to them is still flagged.
- Mark an issue "Not a problem": a new button on each Health issue, with an optional reason. The issue moves to the bottom of the list and out of the count, and stays there when the map is rebuilt. It shows again if the same check finds something new in that file or the issue changes severity, and Show again undoes it. Your choices are saved in floorplan/health-dismissed.json. Exported copies keep the issue set apart but leave your reason out.
- Report a false alarm if you like: a box in the same dialog opens a GitHub issue for you to read, edit and send yourself, with a preview of exactly what it says. It never includes your code or any values, and nothing is sent unless you send it.
Floorplan 0.6.02026-10-31
- Health catches the classic mistakes in AI-built apps. Five new checks, each in plain words with a fix to paste:
- Secret keys sent to the browser: an OpenAI, Stripe or Supabase service-role key (and others) in a NEXTPUBLIC, VITE, REACTAPP_ or similar variable, which every visitor can read. Keys that are public by design, like Supabase's anon key or Stripe's publishable key, are left alone.
- Supabase tables anyone can read and change: tables whose row-level security is never switched on (or is switched off), worked out by replaying the migrations in order, so a table locked later or dropped doesn't count. Policies that let anyone add, change or delete rows are flagged too, as worth a look.
- Firebase rules that let anyone in: Firestore, Storage and Realtime Database rules open to anyone, including "test mode" rules, with the date they stop working (or stopped).
- Stripe webhooks anyone could fake: code that acts on events like checkout.session.completed without checking Stripe's signature, so anyone could send a fake "payment succeeded".
- Servers that let any website call them (CORS): a small note on its own, and worth fixing when login cookies are allowed along with it.
- No more false alarm on Supabase's config.toml: values like "env(S3SECRETKEY)" read a setting from the environment, so they're no longer reported as a key written into the code.
Floorplan 0.5.02026-10-31
- Fits phones and tablets: the top bar wraps instead of running off the screen, the details open as a sheet at the bottom of a phone (tap a box to see them), the long description under the title folds to a line with More / Less, and every control is at least 44 px to tap. Nothing changes with a mouse at 1000 px and wider. Requested in #18 and built by @menachem-kurkus in #19.
- Touch gestures on the map: dragging or pinching on a phone or tablet made the map jump to unexpected places. A drag now follows only the finger that started it and ends when the browser takes over the touch (before, the drag stayed switched on and followed any later movement); a second finger starts a pinch instead of restarting the drag, and a third finger is ignored; two fingers zoom around the point between them and moving both pans; the first tap after a drag is no longer swallowed; and the browser no longer zooms or bounces the page under the map, or re-fits the map when a phone's address bar slides in and out. A mouse, a trackpad and the wheel work exactly as before. Built by @menachem-kurkus in #24.
- No hover tooltip after a tap: a tap also sends the browser's hover event, so a card's tooltip popped up over the details sheet. Tooltips now show only for a mouse, and a tooltip stays inside a narrow window.
Floorplan 0.4.42026-10-31
- The note for future sessions is now your choice: in Claude Code, Floorplan no longer adds its section to CLAUDE.local.md on its own. After your first map, Claude asks whether future sessions in the project should use it, and adds the note only if you say yes. A note you already have is kept up to date; delete it to remove it.
- Pre-approved commands named one by one: the skill now lists each of its eight scripts by name, instead of approving anything in its scripts folder.
Floorplan 0.4.32026-10-31
- Links for the Claude plugin directory: the Claude Code manifest now points to the documentation, the privacy and security page, and GitHub issues for support, so a directory listing shows the right links. Nothing else changed.
Floorplan 0.4.22026-10-30
- Is it safe to install? A new page lists everything Floorplan does on your computer: no hooks, MCP servers, dependencies or downloads, its one outbound request, and every program it runs. A test enforces it on every change, and each release now includes CHECKSUMS.txt, so you can confirm your installed copy matches it (node tools/checksums.mjs --check <folder>).
- Checked by GitHub's code scanner: CodeQL now scans every change. Its first scan found six spots to tighten, all fixed: complete escaping in three places, the "Made with Floorplan" link built without reusing page text as HTML, and plain error messages on the map when Undo or Export fails, with the details in the map server's output.
Read it here: Is it safe to install?