SEC-AUTHZ-01 | Security | Does every server-side write take the caller's identity from the verified session or token, rather than from a user id the client sends in the request body or a hidden form field? | Passed |
SEC-AUTHZ-02 | Security | Does every endpoint that takes a record id check that the calling account is actually allowed to reach that specific record, not just that the caller is logged in? | Passed |
SEC-CORS-01 | Security | Does every API that requires authentication answer CORS with an explicit origin list, rather than a wildcard? | Passed |
SEC-CSP-01 | Security | Does the app send a Content-Security-Policy header, rather than relying only on the framework's default HTML escaping to stop injected scripts? | Partly |
SEC-DEPS-01 | Security | Does the app's dependency tree carry any known-exploited, critical or high-severity vulnerability in a package the running app actually uses on a reachable code path? | Passed |
SEC-KEYS-01 | Security | Is the service-role key, or any other database or admin secret key (a private API token that isn't a model-provider key), kept out of every file the browser bundle can reach, including public env var prefixes? | Passed |
SEC-KEYS-02 | Security | Does the app refuse to start, rather than fall back to a hardcoded or generated default, when a required secret key is missing from the environment? | Passed |
SEC-RATE-01 | Security | Does the login endpoint specifically lock out or slow down repeated failed attempts, rather than relying only on a generic site-wide rate limit? | Failed |
SEC-RATE-02 | Security | Are public, unauthenticated write endpoints (contact forms, sign-up, password reset, comment posting) rate limited and returning 429 once the limit is hit? | Passed |
SEC-REDIRECT-01 | Security | Is the redirect target after login, logout or an auth callback checked against an allowlist of the app's own paths, rather than built directly from a client-supplied parameter? | Passed |
SEC-RLS-01 | Security | Does every table in an exposed schema have row-level security turned on and forced, with a policy for each operation the app actually performs? | Failed |
SEC-RLS-02 | Security | Do the row-level security policies scope rows to the record's owner, rather than granting access to anyone who is simply signed in? | Partly |
SEC-SECRET-01 | Security | Is the working tree and git history free of committed secrets, keys and database dumps? | Passed |
SEC-SESSION-01 | Security | Are session cookies set with HttpOnly, Secure and an appropriate SameSite value? | Passed |
SEC-CALLBACK-01 | Security | Does the sign-in callback (OAuth, or an emailed sign-in link) check the provider's code and state, or the link's token, on the server before it creates a session, instead of trusting whatever the browser sends back? | Passed |
SEC-CSRF-01 | Security | Are state-changing requests authenticated by a cookie protected by a CSRF token, a SameSite setting that blocks cross-site posts, or an Origin check, rather than the cookie alone? | Passed |
SEC-PRICE-01 | Security | Does the server decide the amount, currency and product for every charge, with nothing the browser sends able to change the price, and does charge creation carry an idempotency key so a retry cannot charge twice? | Failed |
SEC-SESSION-02 | Security | Does a session end on logout, expire on its own, and get revoked when the password changes, rather than staying valid indefinitely on an old token? | Passed |
SEC-STORAGE-01 | Security | Are storage buckets private by default, with upload and read policies scoped so a user only reaches their own files, and public buckets used only where the content is genuinely meant to be public? | Not applicable |
SEC-VIEWS-01 | Security | Do database views and SECURITY DEFINER functions carry a stated reason and their own access check, rather than silently running with wider rights and bypassing row-level security underneath? | Passed |
SEC-WEBHOOK-01 | Security | Does every server function correctly classify its caller (a signed-in user, a provider webhook, or a scheduled job) and apply the matching check, instead of one shared authentication path for all three? | Passed |
DATA-BACKUP-01 | Data | Are automated backups running, and has a restore actually been performed and timed at least once? | Passed |
DATA-MIGRATION-01 | Data | Are all schema changes made through versioned migration files, rather than edited directly in a dashboard? | Passed |
DATA-PII-01 | Data | Is the personal data this app collects classified somewhere written down: what is collected and why? | Partly |
DATA-RETENTION-01 | Data | Is there a stated retention and deletion policy, and can a delete request actually be honoured against the database, not just the UI? | Passed |
DATA-TIME-01 | Data | Is every timestamp stored in UTC and converted to the viewer's local time only for display? | Passed |
DATA-TXN-01 | Data | Do multi-step writes that must all succeed together (checkout, account deletion, a role change) run inside one transaction or RPC call, rather than as several sequential client calls? | Passed |
DATA-CONFIG-01 | Data | Is configuration that lives only in a dashboard (auth providers, redirect URLs, custom SMTP, storage limits, scheduled job schedules) written down somewhere the next session or audit can see? | Passed |
DATA-MONEY-01 | Data | Is every monetary amount stored as an integer in the currency's smallest unit, rather than as a float or decimal that gets formatted at storage time? | Passed |
REL-ENV-01 | Reliability | Does a complete .env.example exist, and does every key in it actually exist in the production deployment target, not just locally? | Passed |
REL-ENVSPLIT-01 | Reliability | Do staging and production use separate databases and separate provider keys, rather than sharing one? | Passed |
REL-ERRHANDLE-01 | Reliability | Where a failure is caught, is it logged and surfaced with a safe message, or is the catch block empty and the failure disappears? | Failed |
REL-KILLSWITCH-01 | Reliability | Can any feature that spends money, calls an AI model, or writes to the database be turned off instantly without a code deploy? | Passed |
REL-RETRY-01 | Reliability | Do transient failures on safe-to-repeat outbound calls get retried with backoff, instead of failing the whole request on the first blip? | Partly |
REL-TIMEOUT-01 | Reliability | Does every outbound call the app makes (fetch, an API client, a database driver, a third-party SDK) carry an explicit timeout? | Partly |
REL-BGJOB-01 | Reliability | Does slow work (sending an email, calling a third-party API, processing an upload) run inline in the request, or is it handed off to a queue so the user isn't stuck waiting? | Not applicable |
REL-CIRCUIT-01 | Reliability | When a critical upstream (payment provider, email sender, the app's own backend service) goes down, does the app stop hammering it, or does every page load keep firing requests at a dead service? | Not applicable |
REL-CONNPOOL-01 | Reliability | Is the app's total database connection use, counted across every concurrent build, deploy preview and serverless worker, budgeted against the pooler's project-wide cap? | Passed |
REL-RACE-01 | Reliability | Where two requests can update the same record at once (a stock count, a role, a balance, or an 'at least one must remain' rule like the last admin or last owner), is the update atomic and run inside one locked transaction, rather than a read followed by a separate write? | Passed |
REL-WEBHOOK-01 | Reliability | Does every inbound webhook verify the sender's signature against the raw body, and does replaying the same event twice change nothing the second time? | Passed |
PERF-CACHE-01 | Performance | Are expensive, repeated reads cached with an explicit TTL, and does a write to the underlying data actually invalidate the cached version? | Partly |
PERF-CODESPLIT-01 | Performance | Does the first screen ship only the JavaScript it needs, or is a heavy component (a chart library, a rich editor, an admin-only feature) bundled into every visitor's initial load? | Failed |
PERF-COMPRESS-01 | Performance | Are responses and static assets actually served compressed and with correct cache headers, or is that left to whatever the platform happens to default to? | Passed |
PERF-IMAGE-01 | Performance | Are images served in a modern format, sized for their container, and lazy-loaded below the fold? | Partly |
PERF-PAGINATE-01 | Performance | Do list endpoints and pages (a blog index, a product catalog, a search result set) load a bounded page of results, or do they return everything at once? | Passed |
PERF-INDEX-01 | Performance | Are the columns the app actually filters, sorts, or joins on covered by an index? | Passed |
PERF-NQUERY-01 | Performance | When the app renders a list with related data (posts with authors, orders with line items), does it fetch the related data in one batched query, or does it fire one query per row? | Passed |
SHIP-BUILDERLEFTOVER-01 | Shipping and monitoring | Does the repo carry leftover scaffolding, sample data, or duplicate instruction files from the AI builder that made it (a demo route, seed data still live, conflicting CLAUDE.md/cursorrules/AGENTS.md files that disagree with each other)? | Failed |
SHIP-CI-01 | Shipping and monitoring | Does the gate before deploy run the build, a type check, lint and the test suite, and block the deploy when any of them fails? | Passed |
SHIP-ERRTRACK-01 | Shipping and monitoring | Do exceptions from every part of the app (frontend, backend, background jobs) land in one place with user and request context, or does the operator find out about bugs only when a user reports one? | Failed |
SHIP-LOCKFILE-01 | Shipping and monitoring | Is a lockfile committed and used, so the exact dependency versions installed locally match what the build server installs? | Passed |
SHIP-LOGS-01 | Shipping and monitoring | Are logs structured (JSON, with a request id) so a specific failed request can be traced, or is it free-form text nobody can search? | Passed |
SHIP-TEST-01 | Shipping and monitoring | Do the app's critical paths (checkout, auth, contact/signup) have automated tests that run on every change, or is verification manual only? | Partly |
SHIP-DEPLOYSURFACE-01 | Shipping and monitoring | When the app has more than one deployable surface (a web app, a separate admin backend, database migrations, scheduled jobs), is it documented which of them a push actually redeploys automatically? | Not applicable |
AI-DATA-01 | AI features | Is what user or tenant data reaches the model provider known and kept to the minimum needed, is the provider's data retention setting stated, and does retrieval return only the caller's own tenant's documents? | Not applicable |
AI-EVAL-01 | AI features | Is there an eval set the AI feature's prompt or model gets checked against, or is 'it looked better' the entire test suite for every prompt change? | Not applicable |
AI-INJECT-01 | AI features | Everywhere untrusted text reaches the model (a user message, an uploaded file, a fetched page, another user's record), what stops an instruction hidden in that text from being followed? | Not applicable |
AI-KEY-01 | AI features | Does the AI provider's API key ever reach the browser, in client-side code, a public env var, or a network response? | Not applicable |
AI-MODELPIN-01 | AI features | Is the model version pinned to a specific identifier, or does the code point at a floating alias that can change underneath the app? | Not applicable |
AI-OUTPUTCHECK-01 | AI features | Before the model's output is saved, shown, or acted on, does anything check its shape and content, or does it flow straight through? | Not applicable |
AI-RATELIMIT-01 | AI features | Does a paid AI route limit how often a single user can call it, separately from the spend cap, so one user can't monopolise it or trigger abuse patterns even while staying under the money ceiling? | Not applicable |
AI-SPENDCAP-01 | AI features | Does the AI feature have a per-user and a global spend cap that hard-stops the calls, plus a billing alert on the provider account, or can it run up an unbounded bill? | Not applicable |
PROD-A11Y-01 | Functionality and usability | Can the sign-up or main feature flow be completed using only the keyboard, with no mouse? | Passed |
PROD-A11Y-02 | Functionality and usability | Does every input on the sign-up, sign-in, and main data-entry forms have a label a screen reader can announce? | Passed |
PROD-A11Y-03 | Functionality and usability | Does the body text and the primary call-to-action button meet at least 4.5:1 contrast against their background (3:1 for large text), as rendered on the page? | Partly |
PROD-A11Y-04 | Functionality and usability | Is there a visible focus indicator on every interactive element when navigating by keyboard? | Passed |
PROD-A11Y-05 | Functionality and usability | When text is enlarged to 200 percent, can the landing page, the sign-up form and the main feature screen still be read and used, with nothing cut off or overlapping? | Passed |
PROD-A11Y-06 | Functionality and usability | At 320 CSS pixels wide, does the content reflow into one column, so nothing needs sideways scrolling to read or use? | Failed |
PROD-EASE-01 | Functionality and usability | Is the core flow easy to use as well as working, judged against the UX laws index, with a cost or a standard behind every finding? | Partly |
PROD-DECEPTIVE-01 | Functionality and usability | Does the product work against the person using it anywhere, such as a box ticked before they see it, a cost that appears only at the last step, a decline written to shame, cancelling harder than signing up, or urgency that is not true? | Passed |
PROD-CONSOLE-01 | Functionality and usability | Does the browser console stay free of errors (not warnings) on the landing page, the sign-up or sign-in screen, and the main feature screen? | Passed |
PROD-FLOW-04 | Functionality and usability | Can the app's one main feature, the thing the product exists to do, be completed end to end at desktop and phone width? | Partly |
PROD-MOBILE-01 | Functionality and usability | Do the landing page, the main feature screen, and any form pages hold their layout at phone width with no sideways scroll? | Failed |
PROD-MOBILE-02 | Functionality and usability | Are the primary tap targets (buttons, nav items, form controls) at least 24 by 24 CSS pixels, or spaced as the WCAG 2.2 target-size rule allows, at 390px phone width? | Failed |
PROD-STATE-01 | Functionality and usability | Does every list, dashboard, or search result screen show a real empty state when there is nothing to show, instead of a blank area or a frozen loader? | Partly |
PROD-STATE-02 | Functionality and usability | Does the app show a visible loading indicator during every action that takes more than an instant, rather than leaving the screen looking frozen or unresponsive? | Passed |
PROD-STATE-03 | Functionality and usability | When a request fails, does the user see a plain-language message that says what happened and what to do next, instead of a blank screen, a stuck spinner, or a raw error? | Passed |
PROD-STUB-01 | Functionality and usability | Do the buttons and links on the app's primary screens actually do something, rather than being visual stubs left over from the build? | Failed |
PROD-STUB-02 | Functionality and usability | Do the links in the footer and any secondary navigation, not the primary header navigation checked in PROD-STUB-01, all resolve to a real page rather than a 404 or a placeholder? | Passed |
PROD-FLOW-01 | Functionality and usability | Can a new visitor complete sign-up end to end, in a real browser, at desktop and phone width? | Passed |
PROD-FLOW-02 | Functionality and usability | Can a returning user sign in end to end, in a real browser, at desktop and phone width? | Passed |
PROD-FLOW-03 | Functionality and usability | Can a test purchase be completed end to end, from the pricing or product page through to a confirmed paid state, with no dead end? | Passed |
PROD-FLOW-05 | Functionality and usability | When a user deletes their own account, is their personal data actually deleted or anonymised in the database, not only the account marked deactivated? | Passed |
PROD-FORM-01 | Functionality and usability | Do the app's forms validate input inline and block submission with a clear message, rather than accepting bad data or failing only after a full round trip? | Passed |
PROD-FORM-02 | Functionality and usability | When a form submission fails, does the user's already-typed input stay in place, or does the form clear and force them to start over? | Passed |
PROD-PAY-02 | Functionality and usability | When a test payment is declined, does the app tell the user clearly and let them retry, rather than leaving them stuck with no explanation or silently charging nothing while showing success? | Passed |
PROD-SEO-01 | Functionality and usability | Does every public page carry a unique title, a unique meta description, and a canonical URL, and do internal-only pages carry noindex? | Not applicable |
PROD-SEO-02 | Functionality and usability | When the homepage and a content page are shared on WhatsApp, LinkedIn, or Twitter/X, does the link show a real title, description, and image? | Partly |
PROD-SEO-03 | Functionality and usability | Do sitemap.xml and robots.txt exist at the live domain, load without error, and stay in sync as content is added? | Not applicable |
PROD-SESSION-01 | Functionality and usability | Does refreshing the browser mid-flow, or closing and reopening the tab, keep the user signed in and their in-progress work intact? | Passed |