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.

Spectaculous-Code/raamattu-nyt

https://github.com/Spectaculous-Code/raamattu-nyt · scanned 2026-06-16 04:39 UTC (1 month, 3 weeks ago)

12 raw signals (0 security + 12 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 12 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 0 Medium 6 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 12 Crowd 0 Layer: Frontend 1 Security 5 Cicd 1 Quality 5

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 62.6/100 with 66.7% coverage. It contains 39 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 12 findings — concentrated in security (5), quality (5), frontend (1). Risk profile is high: 3 critical, 0 high, 6 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 11 of 12 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 Runtime dotenv file present in repo: .env.app1

`.env.app1` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.app1 ConfigEnv fileRuntime env

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.app2

`.env.app2` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.app2 ConfigEnv fileRuntime env

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.app3

`.env.app3` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_TURNSTILE_SITE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.

.env.app3 ConfigEnv fileRuntime env

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, ci, tests. 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: license, ci, tests. 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 'cors_wildcard' in README.md:420

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

README.md:420 Cors wildcard

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

0 test file(s) for 5 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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

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/76bdfdad-e6a7-4cbf-a366-f1aa2fc1eed6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/76bdfdad-e6a7-4cbf-a366-f1aa2fc1eed6/

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.