SEAL OF SIGMUNDSECURITY DESKPASSIVE SCANNER · CLOSED EARLY ACCESS
The current product connects an exact repository revision to passive source and dependency findings, declared coverage, and a tenant-bound receipt. Remediation and continuous verification remain product direction, not current scan output.
const query = request.nextUrl.searchParams.get("query")
?? "select 1";
await pool.query(`select * from users where ${query}`);EXACT-REVISION EVIDENCE
Inspect the same receipt structure an evaluator sees: repository identity, scanner versions, findings, coverage, custody, and explicit limitations.
Open the complete receipt →OBSERVED Source path present UNTESTED Runtime not attempted
EVIDENCE VOCABULARY
Request-derived query text reaches the first argument of pool.query at app/api/query/route.ts:13:9.
DIRECT SOURCE EVIDENCEIf the handler is deployed and the query executes with relevant authority, the request value could alter SQL structure.
CONDITIONAL REVIEWER INFERENCEThis state would require a separate controlled test to demonstrate the behavior in an isolated environment.
CONTROLLED TEST EVIDENCENo request was supplied, no database connection was opened, and no query was executed.
DECLARED RUNTIME LIMITATIONTHE MISSING LAYER
Dependency bots, static analysis, and pentests remain useful. Seal of Sigmund is intended to connect signals to applicability, controlled remediation, approval, and verification.
PRODUCT ROADMAP · FULL LIFECYCLE
A concrete anomaly appears in code, configuration, or runtime.
The signal is tied to a component, route, dependency, and revision.
We reproduce it safely—or state exactly why it was not attempted.
Evidence establishes whether the finding applies to your environment.
A bounded remediation includes tests, blast radius, and rollback.
You authorize the exact patch package. Nothing drifts afterward.
After deployment, the result is observed independently.
The invariant remains watched and reopens on regression.
ROADMAP CONCEPT
app/api/query/route.ts:13:9
const query = request.nextUrl.searchParams.get("query")
?? "select 1";
await pool.query(`select * from users where ${query}`);OBSERVED Direct static source evidence
- const query = request.nextUrl.searchParams.get("query")
- await pool.query(`select * from users where ${query}`);
+ const userId = request.nextUrl.searchParams.get("userId");
+ await pool.query(
+ "select * from users where id = $1",
+ [userId],
+ );Assumes the route is meant to look up a user by ID. node-postgres binds values with $1 and a separate values array; authorization, validation, and database privileges remain separate review items.
A future execution mode would bind approval to the exact diff, target, tests, and environment.
View sample receipt format →CONCEPT · NO PATCH AUTHORITYBUILT FOR
Teams shipping continuously without a dedicated application-security department.
Applications where code, dependencies, cloud configuration, and runtime behavior change together.
Teams that need decisions, approvals, and verification they can inspect later.
Code is not sent to a third-party model without explicit, per-job consent.
Isolated and on-premise modes for sensitive codebases remain design commitments.
DESIGN COMMITMENTApproval binds to the exact diff, target, and environment.
Merge and deploy with your tooling and credentials on your schedule.
Repository access is designed around narrow, short-lived authority.
DESIGN COMMITMENTEvery analysis is bounded to one tenant and one authorized job.
DESIGN COMMITMENTRetention windows and deletion behavior will be documented and verifiable.
DESIGN COMMITMENTInstrument failures and blind spots remain visible in the product.
BEFORE YOU ASK FOR ACCESS
Prelaunch means the security gates determine timing. It does not mean quietly changing the scope after you join.
A small, founder-led evaluation of repository connection, passive source and dependency scanning, explicit coverage limits, and tenant-bound receipt workflows. Scope will be agreed before access is granted.
Not automatically. The product is designed around customer approval and customer-controlled execution. Any future execution mode will require a separate, explicit contract.
A founder-approved evaluation may include a bounded three-scan allowance. Continued use is available through a one-time assessment or monthly organization plan; exact pricing and limits are shown before Checkout.
The product is prelaunch. Invitations will follow completed security gates rather than a marketing deadline.
PRELAUNCH · FOUNDER-LED
Request a founder-reviewed early-access place. Approved participants receive a Clerk invitation and prepare a scoped evaluation workspace; product access remains manually granted.