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

ClipboardHealth/core-utils

https://github.com/ClipboardHealth/core-utils · scanned 2026-06-17 01:24 UTC (1 month, 2 weeks ago)

80 raw signals (0 security + 80 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -20.0 (diff) · 78 actionable findings from 1 signal source. 2 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
56.7
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 78 findings
Critical
3
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 3 High 0 Medium 27 Low 46 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 78 Crowd 0 Layer: Api 1 Frontend 24 Network 4 Security 10 Cicd 2 Quality 37
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 56.7/100 with 100.0% coverage. It contains 1677 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 80 findings — concentrated in quality (37), frontend (24), security (12). Risk profile is high: 5 critical, 0 high, 27 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 70 of 78 actionable findings. 80 raw detector signals were grouped into reader-sized issues. 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 2 occurrences Possible secret in packages/analytics/examples/analytics.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 13, 44
packages/analytics/examples/analytics.ts:13, 44 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in packages/analytics/README.md
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 36, 67
packages/analytics/README.md:36, 67 (2 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/util-ts/examples/tryCatchAsync.ts:9
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/util-ts/src/lib/functional/serviceResult.ts:100
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/release.ts:104
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: .claude/settings.json
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.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/commit-push-pr/SKILL.md
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.
plugins/core/skills/commit-push-pr/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/create-groundcrew-ticket/SKILL.md
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.
plugins/core/skills/create-groundcrew-ticket/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/go/SKILL.md
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.
plugins/core/skills/go/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/in-depth-review/SKILL.md
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.
plugins/core/skills/in-depth-review/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/simple-review/SKILL.md
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.
plugins/core/skills/simple-review/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/write-bug-ticket/SKILL.md
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.
plugins/core/skills/write-bug-ticket/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/write-feature-ticket/SKILL.md
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.
plugins/core/skills/write-feature-ticket/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: plugins/core/skills/write-tech-debt-ticket/SKILL.md
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.
plugins/core/skills/write-tech-debt-ticket/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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/ci.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/ai-rules/scripts/execAndLog.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/ai-rules/scripts/execAndLog.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/clearance/src/launcher.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/clearance/src/launcher.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in packages/clearance/src/safehouseClaudeProxyCli.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
packages/clearance/src/safehouseClaudeProxyCli.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in plugins/core/hooks/setupRemoteSession.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
plugins/core/hooks/setupRemoteSession.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/release.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/release.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/syncPlugins.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/syncPlugins.ts:1 Node child process
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docker-compose.yml Ports
medium System graph network Security conf 1.00 Privileged port 48 in use
Port 48 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docker-compose.yml Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 56 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: packages/analytics/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/analytics/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/background-jobs-adapter/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/background-jobs-adapter/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/clearance/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/clearance/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/config/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/config/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/contract-core/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/contract-core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/embedex/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/embedex/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/eslint-plugin/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/eslint-plugin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/example-nestjs/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/example-nestjs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/execution-context/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/execution-context/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/json-api-nestjs/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/json-api-nestjs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/json-api/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/json-api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mongo-jobs/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/mongo-jobs/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/notifications/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/notifications/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/nx-plugin/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/nx-plugin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/phone-number/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/phone-number/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/playwright-reporter-llm/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/playwright-reporter-llm/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/rules-engine/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/rules-engine/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/util-ts/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/util-ts/package.json LockfileReproducibilityGenerated repo pattern
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/ai-rules/scripts/build.ts:21
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 — packages/ai-rules/scripts/execAndLog.ts:25
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 — packages/ai-rules/scripts/populateReadme.ts:32
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 — packages/ai-rules/scripts/sync.ts:65
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 — packages/contract-core/examples/schemas.ts:42
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 — packages/embedex/src/lib/embed.test.ts:11
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 — packages/execution-context/examples/executionContext.ts:23
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 — packages/mongo-jobs/examples/usage/jobs/cleanupJob.ts:14
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 — packages/mongo-jobs/examples/usage/jobs/dailyReportJob.ts:13
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 — packages/mongo-jobs/examples/usage/jobs/emailJob.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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/mongo-jobs/examples/usage/jobs/processUserJob.ts:13
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 — packages/mongo-jobs/examples/usage/jobs/reportJob.ts:14
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 — packages/mongo-jobs/examples/usage/jobs/sendEmailJob.ts:14
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 — packages/mongo-jobs/examples/usage/jobs/smsJob.ts:14
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 — packages/mongo-jobs/examples/usage/myJob.ts:19
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 — packages/mongo-jobs/examples/usage/registerJobsWithDependencies.ts:11
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 — packages/phone-number/src/lib/formatPhoneNumber.ts:28
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 — packages/playwright-reporter-llm/src/lib/internal/testResults.test.ts:71
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 — packages/playwright-reporter-llm/src/lib/reporter.test.ts:614
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 — packages/util-ts/src/lib/strings/parseJson.ts:13
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 — plugins/core/hooks/setupRemoteSession.ts:49
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 — populateLibraries.ts:93
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 — scripts/release.ts:51
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 — scripts/syncPlugins.ts:112
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 quality Complexity conf 1.00 Very large file: packages/notifications/src/lib/notificationClient.test.ts (1860 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/9358ebad-f73b-4abb-82c1-dfdd61b1ba6b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9358ebad-f73b-4abb-82c1-dfdd61b1ba6b/

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.