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

sidthesloth92/db-astro-suite

https://github.com/sidthesloth92/db-astro-suite · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

112 raw signals (53 security + 59 graph)

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

Complete repo analysis

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

JSON
Combined
65.7
/100
Security checks
66
9 findings
System graph
66
100.0% cov · 48 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 3 Medium 14 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 48 Crowd 0 Layer: Quality 36 Cicd 5 Security 5 Frontend 5 Hardware 3 Api 3
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 65.7/100 with 100.0% coverage. It contains 1339 nodes across 19 cross-layer flows, written primarily in mixed languages. Engine surfaced 59 findings — concentrated in quality (29), cicd (14), frontend (5). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 40 of 57 actionable findings. 225 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 cicd CI/CD security conf 0.86 Foundry mined claimed resolved with failing ci: sidthesloth92/db-astro-suite
Graph query export: Claimed resolved with failing CI Query id: claimed_resolved_with_failing_ci Query type: motif_query Intent: Hard negatives where CI/failure evidence contradicts a resolution claim. Motif: claimed_resolved_with_failing_ci Training usage: hard_negative Graph gold label: contradict…
CI/CD securityCI/CD
critical Security checks quality Practices conf 0.82 4 occurrences Foundry mined mock as real or placeholder: sidthesloth92/db-astro-suite
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
4 occurrences
repo-level (4 hits)
critical Security checks security auth conf 0.78 5 occurrences Foundry mined security auth guardrail gaps: sidthesloth92/db-astro-suite
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
5 occurrences
repo-level (5 hits)
high Security checks quality Practices conf 0.84 9 occurrences Foundry mined bad chains: sidthesloth92/db-astro-suite
Comment chain pattern product: bad_chains Repo: sidthesloth92/db-astro-suite Thread: sidthesloth92/db-astro-suite#7 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_arti…
9 occurrences
repo-level (9 hits)
high Security checks quality Quality conf 0.76 6 occurrences Foundry mined schema ui api mismatch: sidthesloth92/db-astro-suite
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
6 occurrences
repo-level (6 hits)
high Security checks quality Testing conf 0.78 20 occurrences Foundry mined test ci gap after feedback: sidthesloth92/db-astro-suite
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
20 occurrences
repo-level (20 hits)
medium Security checks quality Practices conf 0.62 64 occurrences Foundry mined assumption checks: sidthesloth92/db-astro-suite
Comment chain pattern product: assumption_checks Repo: sidthesloth92/db-astro-suite Thread: sidthesloth92/db-astro-suite#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, …
64 occurrences
repo-level (64 hits)
medium Security checks quality maintenance conf 0.70 36 occurrences Foundry mined blueprint gap alignment: sidthesloth92/db-astro-suite
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
36 occurrences
repo-level (36 hits)
medium Security checks quality Practices conf 0.70 21 occurrences Foundry mined unresolved feedback: sidthesloth92/db-astro-suite
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
21 occurrences
repo-level (21 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/astrogram/src/app/services/astro-info.service.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 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, 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 hardware Security conf 1.00 Dockerfile runs as root: tools/astrosolve/server/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 57, 257, 264, 285
.github/workflows/pipeline.yml:57, 257, 264, 285 (4 hits)
CI/CD securitySupply chainGithub actions
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/pipeline.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in tools/astrogram/src/app/services/astro-info.service.ts:22
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
tools/astrogram/src/app/services/astro-info.service.ts:22 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in libs/ui/src/lib/constellation-loader/constellation-loader.component.ts:68
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
libs/ui/src/lib/constellation-loader/constellation-loader.component.ts:68 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/astrosolve/server/src/utils/command-runner.util.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/astrosolve/server/src/utils/command-runner.util.js:1 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
29 test file(s) for 352 source file(s) (ratio 0.08). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 33 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 hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 4, 18
tools/astrosolve/server/Dockerfile:4, 18 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 43, 62, 142, 196, 199, 213, 219, 235
.github/workflows/pipeline.yml:43, 62, 142, 196, 199, 213, 219, 235 (8 hits)
CI/CD securitySupply chainGithub actions
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 quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: hub/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.
hub/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: libs/ui/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.
libs/ui/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: tools/astrogram/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.
tools/astrogram/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: tools/astrosolve/server/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.
tools/astrosolve/server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: tools/starwizz/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.
tools/starwizz/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rest_v1` in tools/astrogram/src/app/services/astro-info.service.ts:7
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 — tools/astrogram/src/app/components/base-card-preview/base-card-preview.ts:287
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 — tools/astrosolve/server/scripts/analytics.js: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 — tools/astrosolve/server/scripts/manage-keys.js:27
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 api Wiring conf 1.00 Unused endpoint: GET /
`tools/astrosolve/server/src/index.js` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/limits
`tools/astrosolve/server/src/index.js` declares `GET /api/v1/limits` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/solve
`tools/astrosolve/server/src/routes/solve.route.js` declares `POST /api/v1/solve` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
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/32929252-fd11-474c-a4d4-f98be3697996/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/32929252-fd11-474c-a4d4-f98be3697996/

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.