msitarzewski/agency-agents

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.

1 of your 3 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.76s · analysis 0.82s · 3.4 MB · GitHub preflight 426ms

https://github.com/msitarzewski/agency-agents · scanned 2026-06-05 05:48 UTC (2 hours, 1 minute ago) · 10 languages

8 findings (2 legacy + 6 scanner) 95th percentile · Unknown · Scanner says 100 (lower by 24)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 hours, 1 minute ago · v2 · 5 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	45.0	0.15	6.75
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	70.0	0.15	10.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	75.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 2 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 2 9-layer 3 Crowd 0 Layer: Software 2 Api 1 Frontend 1 Security 1

Exclude dismissed / FP Exclude test files

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 99.7/100 with 66.7% coverage. It contains 311 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 3 findings — concentrated in api (1), frontend (1), security (1). Risk profile is low: 0 critical, 0 high, 1 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high Legacy software dependency conf 0.90 ✓ Repobility Action `actions/checkout` pinned to mutable ref `@v4`

`uses: actions/checkout@v4` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lock with Dependabot or renovate.

.github/workflows/lint-agents.yml:27 dependencylegacy

medium Legacy software dependency conf 0.90 GitHub Action `actions/checkout@v4` is 2 major version(s) behind (latest v6.0.3)

`uses: actions/checkout@v4` is 2 major version(s) behind the latest published release v6.0.3. Old action majors run on deprecated runner images / Node versions and miss upstream fixes. This is the exact 'outdated GitHub Action' class Dependabot raises — and which Repobility had no coverage for.

.github/workflows/lint-agents.yml:27 dependencylegacy

medium 9-layer security coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.

coverageauth

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/69d4b50a-024f-475b-874c-c884ad6a983f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/69d4b50a-024f-475b-874c-c884ad6a983f/

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.