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
40 of your 82 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.8s · analysis 18.69s · 6.1 MB · GitHub API rate-limit (preflight)

0gam24/moneylook

https://github.com/0gam24/moneylook · scanned 2026-06-16 03:37 UTC (2 months ago) · 10 languages

116 raw signals (77 security + 39 graph) 50th percentile · Typescript · small (2-20K LoC) System graph score 54 (higher by 22)

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

Complete repo analysis

Last scanned 2 months ago · v1 · 65 actionable findings from 2 signal sources. 51 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
66.2
/100
Security checks
78
36 findings
System graph
54
88.9% cov · 29 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 58.1 0.25 14.53
testing_score 100.0 0.20 20.00
documentation_score 48.0 0.15 7.20
practices_score 79.0 0.15 11.85
code_quality 74.8 0.10 7.48
Overall 1.00 76.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 12 Medium 22 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 36 System graph 29 Crowd 0 Layer: Software 20 Security 10 Cicd 5 Quality 25 Network 5
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 54.3/100 with 88.9% coverage. It contains 516 nodes across 12 cross-layer flows, written primarily in mixed languages. Engine surfaced 39 findings — concentrated in quality (16), cicd (12), security (6). Risk profile is low: 0 critical, 0 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 50 of 65 actionable findings. 116 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 Security checks security secrets conf 0.95 Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
Gitleaks detected a committed secret or credential pattern.
docs/14-security.md:194
critical Security checks security secrets conf 0.95 Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
Gitleaks detected a committed secret or credential pattern.
.env.example:20
high Security checks software dependencies conf 0.88 devalue: GHSA-77vg-94rm-hx3p
Svelte devalue: DoS via sparse array deserialization
pnpm-lock.yaml
high Security checks software dependencies conf 0.88 esbuild: GHSA-gv7w-rqvm-qjhr
esbuild: Missing binary integrity verification in Deno module enables remote code execution via NPM_CONFIG_REGISTRY
pnpm-lock.yaml
high Security checks software dependencies conf 0.88 fast-xml-builder: GHSA-5wm8-gmm8-39j9
fast-xml-builder allows attribute values with unwanted quotes to bypass malicious or unwanted attributes
pnpm-lock.yaml
high Security checks software dependencies conf 0.88 vite: GHSA-fx2h-pf6j-xcff
vite: `server.fs.deny` bypass on Windows alternate paths
pnpm-lock.yaml
high Security checks software dependencies conf 0.88 ws: GHSA-96hv-2xvq-fx4p
ws: Memory exhaustion DoS from tiny fragments and data chunks
pnpm-lock.yaml
medium Security checks software dependencies conf 0.88 fast-xml-builder: GHSA-45c6-75p6-83cc
fast-xml-builder Comment Value regex can be bypassed
pnpm-lock.yaml
medium Security checks cicd CI/CD security conf 0.90 ✓ Repobility 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `pnpm/action-setup` pinned to mutable ref `@v4` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
4 files, 7 locations
.github/workflows/secrets-scan.yml:40, 52 (3 hits)
.github/workflows/lighthouse-ci.yml:24, 50 (2 hits)
.github/workflows/go-live-check.yml:36
.github/workflows/security-audit.yml:27
CI/CD securitySupply chainGitHub Actions
medium Security checks software dependencies conf 0.88 js-yaml: GHSA-h67p-54hq-rp68
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases
pnpm-lock.yaml
high Security checks software dependencies conf 0.90 npm package `@astrojs/mdx` is 1 major version(s) behind (^5.0.4 -> 6.0.3)
`@astrojs/mdx` is pinned/resolved at ^5.0.4 but the latest stable release on the npm registry is 6.0.3 (1 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
high Security checks software dependencies conf 0.90 npm package `@types/react-dom` is 1 major version(s) behind (^18.3.1 -> 19.2.3)
`@types/react-dom` is pinned/resolved at ^18.3.1 but the latest stable release on the npm registry is 19.2.3 (1 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
medium Security checks software dependencies conf 0.88 vite: GHSA-v6wh-96g9-6wx3
launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows
pnpm-lock.yaml
medium Security checks software dependencies conf 0.88 ws: GHSA-58qx-3vcg-4xpx
ws: Uninitialized memory disclosure
pnpm-lock.yaml
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/audit/gsc-opportunities.mjs:52
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/audit/revenue-pull.mjs: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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/rss-agent.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.
.claude/agents/rss-agent.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.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.
CLAUDE.md VerificationClaude 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 license, operator-readme. 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 cicd CI/CD security conf 1.00 3 occurrences 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.
3 files, 3 locations
.github/workflows/auto-create-pr.yml
.github/workflows/auto-merge.yml
.github/workflows/daily-rebuild.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/pages/api/qa.json.ts:70
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/pages/api/qa.json.ts:70 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/audit/backfill-published-dates.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/audit/backfill-published-dates.mjs:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/audit/distribute-published-dates.mjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/audit/distribute-published-dates.mjs:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/install-hooks.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/install-hooks.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/secrets-scan.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/secrets-scan.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/setup-env.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/setup-env.mjs:15 Node child process
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/scheduled-rebuild.yml Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/scheduled-rebuild.yml Ports
medium System graph network Security conf 1.00 Privileged port 18 in use
Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/secrets-scan.yml Ports
medium System graph network Security conf 1.00 Privileged port 21 in use
Port 21 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/daily-rebuild.yml Ports
medium System graph network Security conf 1.00 Privileged port 3 in use
Port 3 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/secrets-scan.yml Ports
low Security checks software dependencies conf 0.88 @babel/core: GHSA-4x5r-pxfx-6jf8
@babel/core: Arbitrary File Read via sourceMappingURL Comment
pnpm-lock.yaml
low Security checks quality Quality conf 0.60 8 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
6 files, 8 locations
src/pages/og/[cluster]/[slug].svg.ts:1, 5 (2 hits)
src/pages/sitemap-news.xml.ts:1, 3 (2 hits)
src/pages/atom.xml.ts:11
src/pages/feed.json.ts:4
src/pages/og-square/[cluster]/[slug].svg.ts:5
src/pages/sitemap-images.xml.ts:3
duplicationquality
low Security checks software dependencies conf 0.88 esbuild: GHSA-g7r4-m6w7-qqqr
esbuild allows arbitrary file read when running the development server on Windows
pnpm-lock.yaml
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 26 occurrences GitHub Action is tag-pinned rather than SHA-pinned
Action `actions/checkout` pinned to mutable ref `@v4` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.
7 files, 26 locations
.github/workflows/security-audit.yml:26, 31, 59, 122 (6 hits)
.github/workflows/go-live-check.yml:35, 40, 143 (4 hits)
.github/workflows/lighthouse-ci.yml:23, 28, 49, 54 (4 hits)
.github/workflows/secrets-scan.yml:35, 51, 56, 69 (4 hits)
.github/workflows/stale-content-check.yml:21, 22, 46 (4 hits)
.github/workflows/ci.yml:108, 133, 148 (3 hits)
.github/workflows/auto-create-pr.yml:34
CI/CD securitySupply chainGitHub Actions
low Security checks quality Documentation No LICENSE file
Add a LICENSE file to your repository. Use choosealicense.com to pick the right license (MIT for permissive, Apache 2.0 for patent protection, GPL for copyleft).
high Security checks software dependencies conf 0.90 npm package `pagefind` is minor version(s) behind (^1.4.0 -> 1.5.2)
`pagefind` is pinned/resolved at ^1.4.0 but the latest stable release on the npm registry is 1.5.2 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
high Security checks software dependencies conf 0.90 npm package `web-vitals` is minor version(s) behind (^5.2.0 -> 5.3.0)
`web-vitals` is pinned/resolved at ^5.2.0 but the latest stable release on the npm registry is 5.3.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
low Security checks cicd CI/CD security conf 0.35 ✓ Repobility 2 occurrences Workflow references repository secrets in a pull_request workflow
Fork pull_request runs do not receive normal repository secrets on GitHub Actions. Review this as a reliability/intent signal, not as direct fork-secret exfiltration. Raise severity only for pull_request_target or another trusted-context path that runs untrusted PR code with secrets.
lines 42, 68
.github/workflows/lighthouse-ci.yml:42, 68 (2 hits)
CI/CD securityworkflow secretsGitHub Actions
low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CF_PAGES_COMMIT_SHA`, `CI`, `DRY_RUN`, `FAIL_ON_WARN`, `PUBLIC_SENTRY_SAMPLE_RATE`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 226 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 Tests conf 1.00 Low test-to-source ratio
13 tests / 55 src (ratio 0.24).
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated 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 quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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
high Security checks software dependencies conf 0.90 npm package `@astrojs/react` is patch version(s) behind (^5.0.4 -> 5.0.7)
`@astrojs/react` is pinned/resolved at ^5.0.4 but the latest stable release on the npm registry is 5.0.7 (patch version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
high Security checks software dependencies conf 0.90 npm package `@astrojs/sitemap` is patch version(s) behind (^3.7.2 -> 3.7.3)
`@astrojs/sitemap` is pinned/resolved at ^3.7.2 but the latest stable release on the npm registry is 3.7.3 (patch version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
high Security checks software dependencies conf 0.90 npm package `@vitest/coverage-v8` is patch version(s) behind (^4.1.5 -> 4.1.9)
`@vitest/coverage-v8` is pinned/resolved at ^4.1.5 but the latest stable release on the npm registry is 4.1.9 (patch version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.
package.json
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/6c9075fa-1280-4eb0-8a20-5046b98eee3f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6c9075fa-1280-4eb0-8a20-5046b98eee3f/

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.