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.
Sign up free Scan another repo

grest-ts/grest-ts

https://github.com/grest-ts/grest-ts · scanned 2026-06-16 04:25 UTC (2 months ago)

22 raw signals (0 security + 22 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
68.1
/100
Security checks
68
0 findings
System graph
68
77.8% cov · 22 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 2 Medium 7 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 22 Crowd 0 Layer: Frontend 6 Security 9 Quality 7
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 68.1/100 with 77.8% coverage. It contains 69 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 22 findings — concentrated in security (9), quality (7), frontend (6). Risk profile is high: 2 critical, 2 high, 7 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in AGENTS.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
AGENTS.md:320
critical System graph security Secrets conf 1.00 Possible secret in CLAUDE.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
CLAUDE.md:320
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: AGENTS.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
AGENTS.md:507 SecretsAgents md
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:507 SecretsClaude instruction
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 ci, tests, 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in grest.1.check.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
grest.1.check.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in grest.3.ver.patch.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
grest.3.ver.patch.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in grest.4.build.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
grest.4.build.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in grest.5.npm.publish.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
grest.5.npm.publish.ts:7 Node child process
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 47 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 Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: 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.
package.json LockfileReproducibilityGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — grest.1.check.ts:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — grest.2.vitest.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — grest.3.ver.patch.ts:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — grest.4.build.ts:315
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — grest.5.npm.publish.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/a8537c17-791b-469f-a479-4f4d02087b49/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a8537c17-791b-469f-a479-4f4d02087b49/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.