Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

tombeckenham/modelschemas

https://github.com/tombeckenham/modelschemas · scanned 2026-06-16 00:39 UTC (2 months, 1 week ago)

45 raw signals (0 security + 45 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 45 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 45 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 12 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 45 Crowd 0 Layer: Api 1 Frontend 14 Security 1 Cicd 1 Quality 28

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 82.2/100 with 100.0% coverage. It contains 933 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 45 findings — concentrated in quality (28), frontend (14), api (1). Risk profile is low: 0 critical, 0 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 37 of 45 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/cli/src/agent-auth.ts:17

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/cli/src/index.ts:99

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/agent-roundtrip.ts:26

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/webmcp.ts:94

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/server/providers/fal.ts:105

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/server/providers/types.ts:101

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/worker.ts:36

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .cursorrules

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.cursorrules VerificationCursor rule

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skill/modelschemas/SKILL.md

skill/modelschemas/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/seed.ts:7

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/seed.ts:7 Node child process

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 21 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/image-dimensions/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

examples/image-dimensions/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/schema-studio/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

examples/schema-studio/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/video-composer/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

examples/video-composer/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/cli/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/cli/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/vite/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

packages/vite/package.json LockfileReproducibilityGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `includeDeprecated` in src/routes/v1/models/index.ts:32

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `includeDeprecated` in src/server/catalog.ts:23

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `includeDeprecated` in src/server/catalog.worker.test.ts:86

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/cli/src/index.ts:73