infosecstreams/infosecstreams.github.io

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

Scan timing: clone 1.55s · analysis 0.57s · 0.9 MB · GitHub preflight 437ms

infosecstreams/infosecstreams.github.io

https://github.com/infosecstreams/infosecstreams.github.io · scanned 2026-06-05 18:19 UTC (4 days, 19 hours ago) · 10 languages

12 raw signals (4 security + 8 graph) 69th percentile · Javascript · tiny (<2K LoC) System graph score 99 (lower by 26)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 8 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 4 findings

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`	60.0	0.15	9.00
`practices_score`	70.0	0.15	10.50
`code_quality`	70.0	0.10	7.00
Overall		1.00	72.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

Scan summary Quality grade B (72/100). Dimensions: security 100, maintainability 45. 4 findings (2 security). 238 lines analyzed.

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

low Security checks cicd CI/CD security conf 0.90 ✓ Repobility GitHub Action is tag-pinned rather than SHA-pinned

Action `actions/checkout` pinned to mutable ref `@v3` uses a mutable tag or branch. Pin external actions to a reviewed full commit SHA when the workflow is security-sensitive.

.github/workflows/main.yaml:24 CI/CD securitySupply chainGitHub Actions

medium Security checks quality Error handling conf 1.00 [ERR002] Empty Catch Block: Empty catch blocks hide errors.

Log the error or rethrow it. Use console.error() at minimum.

js/sort.js:238

high Security checks software dependencies conf 0.90 GitHub Action `actions/checkout@v3` is 3 major version(s) behind (latest v6.0.3)

`uses: actions/checkout@v3` is 3 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/main.yaml:24

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.). Either auth lives in custom code, in a separate service, or is missing.

auth

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

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

Coverage

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/d59ef752-3f00-45ae-a85c-7cf83affbc5c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d59ef752-3f00-45ae-a85c-7cf83affbc5c/

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.