jaywcjlove/awesome-mac

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.

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

Scan timing: clone 2.97s · analysis 2.56s · 1.3 MB · GitHub preflight 406ms

https://github.com/jaywcjlove/awesome-mac · scanned 2026-06-05 05:52 UTC (8 hours, 38 minutes ago) · 10 languages

29 findings (15 legacy + 14 scanner) 95th percentile · Unknown · Scanner says 84 (lower by 9)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 8 hours, 38 minutes ago · v2 · 22 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`	65.0	0.15	9.75
`security_score`	94.4	0.25	23.60
`testing_score`	70.0	0.20	14.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	75.0	0.15	11.25
`code_quality`	79.0	0.10	7.90
Overall		1.00	75.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 10 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 15 9-layer 7 Crowd 0 Layer: Cicd 4 Software 10 Quality 2 Api 1 Hardware 3 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 84.1/100 with 77.8% coverage. It contains 45 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in hardware (3), api (1), frontend (1). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the hardware layer findings first — that's where the highest-impact wins live.

Showing 19 of 22 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 `@v6`

`uses: actions/checkout@v6` 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/ci.yml:13 dependencylegacy

high Legacy software dependency conf 0.90 ✓ Repobility Action `actions/setup-node` pinned to mutable ref `@v6`

`uses: actions/setup-node@v6` 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/ci.yml:16 dependencylegacy

high Legacy software dependency conf 0.90 ✓ Repobility Dockerfile FROM `lipanski/docker-static-website:latest` not pinned by digest

`FROM lipanski/docker-static-website:latest` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.

Dockerfile:3 dependencylegacy

medium Legacy cicd docker conf 0.90 Docker build context has no .dockerignore

Without .dockerignore, build context can include source history, local env files, dependencies, and generated artifacts.

.dockerignore dockerlegacy

high Legacy cicd docker conf 0.82 Docker final stage has no non-root USER

Docker images run as root unless the image or Dockerfile switches to a non-root user.

Dockerfile:3 dockerlegacy

medium Legacy cicd docker conf 0.94 Dockerfile base image uses the latest tag

The latest tag is mutable and can change without a code review, producing different images from the same source.

Dockerfile:3 dockerlegacy

medium Legacy software dependency conf 0.90 npm package `fs-extra` is 1 major version(s) behind (^10.1.0 -> 11.3.5)

`fs-extra` is pinned/resolved at ^10.1.0 but the latest stable release on the npm registry is 11.3.5 (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 dependencylegacy

medium Legacy software dependency conf 0.90 npm package `remark-gfm` is 1 major version(s) behind (^3.0.1 -> 4.0.1)

`remark-gfm` is pinned/resolved at ^3.0.1 but the latest stable release on the npm registry is 4.0.1 (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 dependencylegacy

medium Legacy software dependency conf 0.90 npm package `remark` is 1 major version(s) behind (^14.0.2 -> 15.0.1)

`remark` is pinned/resolved at ^14.0.2 but the latest stable release on the npm registry is 15.0.1 (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 dependencylegacy

medium Legacy software dependency conf 0.90 npm package `to-vfile` is 1 major version(s) behind (^7.2.3 -> 8.0.0)

`to-vfile` is pinned/resolved at ^7.2.3 but the latest stable release on the npm registry is 8.0.0 (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 dependencylegacy

medium 9-layer hardware supply-chain conf 1.00 Docker base image uses a mutable or implicit tag: lipanski/docker-static-website:latest

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:3 supply-chaindockerpinned-dependencies

medium 9-layer hardware security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

securitycontainer

medium 9-layer cicd supply-chain 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/ci.yml supply-chaingithub-actionsleast-privilege

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

low Legacy quality quality conf 0.70 Generated build artifact directory is present at repository root

Committed build outputs and caches make scans slower, confuse duplicate-code checks, and give AI agents stale generated code to imitate.

dist:1 qualitylegacy

low Legacy quality quality conf 0.70 Generated build artifact directory is present at repository root

Committed build outputs and caches make scans slower, confuse duplicate-code checks, and give AI agents stale generated code to imitate.

build:1 qualitylegacy

low Legacy software dependency conf 0.90 GitHub Action `actions/setup-node@v6` is minor version(s) behind (latest v6.4.0)

`uses: actions/setup-node@v6` is minor version(s) behind the latest published release v6.4.0. 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/ci.yml:16 dependencylegacy

low Legacy software dependency conf 0.90 npm package `idoc` is minor version(s) behind (^1.26.5 -> 1.34.4)

`idoc` is pinned/resolved at ^1.26.5 but the latest stable release on the npm registry is 1.34.4 (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 dependencylegacy

low 9-layer 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.

coveragedeployment

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/780d0553-b604-49e0-85ef-2344b5fb6c0e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/780d0553-b604-49e0-85ef-2344b5fb6c0e/

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.