1. Crawl Summary

No findings.

2. Data Found

No data collected yet.

3. Homepage Audit

No findings.

4. Content Quality

No findings.

5. Schema / Structured Data Audit

No findings.

6. Links & Images

No findings.

7. Performance

No findings.

8. Security

No findings.

9. robots.txt and sitemap.xml Audit

No findings.

10. LLM / AI Crawler Accessibility

No findings.

11. Generative Engine Optimization (GEO)

No findings.

12. Positioning Clarity

No findings.

13. Foundations

No findings.

14. Accessibility

No findings.

15. Well-Known URIs

No findings.

16. Privacy

No findings.

17. Resilience

No findings.

18. Website Specification

No findings.

19. Missing or Hard-to-Find Information

No findings.

20. Recommended Fixes

No findings.

21. Priority To-Do List

No findings.

22. Slop Score

• fail

  Code — 9 pages share 2 duplicate meta descriptions

  Give every page a unique meta description describing that page specifically. Duplicates tell an answer engine the pages are interchangeable, so it picks one and drops the rest.

  Evidence

  {
    "count": 9,
    "weight": 10,
    "samples": [
      "\"sign in with github to manage your vu1nz subscriptions, scan\" × 5 (https://vu1nz.com/login)",
      "\"github is where people build software. more than 150 million\" × 4 (https://vu1nz.com/api/auth/github)"
    ],
    "dimension": "code"
  }

  P2
• fail

  Design — 20 pages share one defect: images have no width/height — causes layout shift

  This appears on 20 of the 50 pages crawled, which means it lives in a shared template or component rather than in the content. Fix it once there and every page is fixed. Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "urls": [
      "https://vu1nz.com/blog/security-awareness-training-ci-cd-software-supply-chain",
      "https://vu1nz.com/blog/vivint-security-ci-cd-supply-chain-defense",
      "https://vu1nz.com/blog/security-license-ci-cd-architecture",
      "https://vu1nz.com/blog/security-testing-cicd-supply-chain-architecture",
      "https://vu1nz.com/blog/protective-security-specialist-cicd-supply-chain",
      "https://vu1nz.com/blog/cyber-security-analyst-jobs-cicd-supply-chain-2026",
      "https://vu1nz.com/blog/securitas-security-services-usa-cicd-security-architecture",
      "https://vu1nz.com/blog/security-systems-ci-cd-software-supply-chain",
      "https://vu1nz.com/blog/security-public-storage-cicd-workflow",
      "https://vu1nz.com/blog/vector-security-ci-cd-supply-chain",
      "https://vu1nz.com/blog/adt-security-ci-cd-automated-detection-triage",
      "https://vu1nz.com/blog/cyber-security-certifications-devsecops-architecture-guide",
      "https://vu1nz.com/blog/identity-and-access-management-for-cloud-security",
      "https://vu1nz.com/blog/ai-agents-github-actions-security",
      "https://vu1nz.com/blog/adt-home-security-cicd-supply-chain-defense",
      "https://vu1nz.com/blog/encrypted-messaging-github-actions-security",
      "https://vu1nz.com/blog/security-service-ci-cd-supply-chain-defense",
      "https://vu1nz.com/blog/screen-sharing-ci-cd-security",
      "https://vu1nz.com/blog/security-service-architecture-cicd-supply-chain",
      "https://vu1nz.com/blog/trane-supply-ci-cd-supply-chain-security"
    ],
    "pages": 20,
    "issueKey": "design.unsized_images",
    "systemic": true,
    "dimension": "design"
  }

  P2
• fail

  Code — 9 pages share 2 duplicate titles

  Give every page a unique title describing that page specifically. Duplicates tell an answer engine the pages are interchangeable, so it picks one and drops the rest.

  Evidence

  {
    "count": 9,
    "weight": 10,
    "samples": [
      "\"sign in · vu1nz\" × 5 (https://vu1nz.com/login)",
      "\"sign in to github · github\" × 4 (https://vu1nz.com/api/auth/github)"
    ],
    "dimension": "code"
  }

  P2
• warn

  Content — 5 pages with no <h1>

  Add one H1 per page stating what the page is about. Answer engines use it as the page's headline claim.

  Evidence

  {
    "count": 5,
    "weight": 7,
    "samples": [
      "https://vu1nz.com/compare",
      "https://vu1nz.com/api/auth/github",
      "https://vu1nz.com/api/auth/github?next=%2Fdashboard",
      "https://vu1nz.com/api/auth/github?next=%2Fapi%2Fgithub%2Fapp%2Finstall",
      "https://vu1nz.com/api/auth/github?next=%2Fdashboard%2Fapi-keys"
    ],
    "dimension": "content"
  }

  P3
• warn

  /blog/security-awareness-training-ci-cd-software-supply-chain — 2 issues (13 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (1×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines. **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-awareness-training-ci-cd-software-supply-chain",
    "words": 3574,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 1,
        "label": "Unrendered {{template}} variable rendered on the page (1×)",
        "samples": [
          "{{ github.event.pull_request.head.sha }}"
        ],
        "dimension": "code"
      },
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 13
  }

  P3
• warn

  /blog/vivint-security-ci-cd-supply-chain-defense — 2 issues (13 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (1×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines. **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/vivint-security-ci-cd-supply-chain-defense",
    "words": 3512,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 1,
        "label": "Unrendered {{template}} variable rendered on the page (1×)",
        "samples": [
          "{{ github.event.pull_request.head.sha }}"
        ],
        "dimension": "code"
      },
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 13
  }

  P3
• warn

  /blog/security-license-ci-cd-architecture — 2 issues (13 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (2×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines. **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-license-ci-cd-architecture",
    "words": 3852,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 2,
        "label": "Unrendered {{template}} variable rendered on the page (2×)",
        "samples": [
          "{{ steps.diff.outputs.needs_scan }}",
          "{{ secrets.SECURITY_LICENSE_KEY }}"
        ],
        "dimension": "code"
      },
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 13
  }

  P3
• warn

  /blog/security-testing-cicd-supply-chain-architecture — 2 issues (13 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (1×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines. **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-testing-cicd-supply-chain-architecture",
    "words": 3380,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 1,
        "label": "Unrendered {{template}} variable rendered on the page (1×)",
        "samples": [
          "{{ github.event.pull_request.head.sha }}"
        ],
        "dimension": "code"
      },
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 13
  }

  P3
• warn

  Content — 2 pages are near-duplicates of each other (1 pair ≥70% identical)

  Consolidate these into one strong page and redirect the rest, or rewrite each to cover something genuinely different. Near-duplicate pages are the clearest fingerprint of scaled content, and they compete with each other instead of ranking.

  Evidence

  {
    "count": 2,
    "weight": 6,
    "samples": [
      "75% — https://vu1nz.com/ ≈ https://vu1nz.com/compare"
    ],
    "dimension": "content"
  }

  P3
• warn

  Code — 7 pages share one defect: Unrendered {{template}} variable rendered on the page (1×)

  This appears on 7 of the 50 pages crawled, which means it lives in a shared template or component rather than in the content. Fix it once there and every page is fixed. Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.

  Evidence

  {
    "urls": [
      "https://vu1nz.com/blog/security-awareness-training-ci-cd-software-supply-chain",
      "https://vu1nz.com/blog/vivint-security-ci-cd-supply-chain-defense",
      "https://vu1nz.com/blog/security-license-ci-cd-architecture",
      "https://vu1nz.com/blog/security-testing-cicd-supply-chain-architecture",
      "https://vu1nz.com/",
      "https://vu1nz.com/compare",
      "https://vu1nz.com/github-actions"
    ],
    "pages": 7,
    "issueKey": "code.leaked_value",
    "systemic": true,
    "dimension": "code"
  }

  P3
• warn

  /faq — 1 issue (5 slop points)

  **Content: Almost no first-party evidence (1 signal of 6)** Add at least two things only you could publish: a real metric with its source, a named customer quote, a comparison table, a screenshot of your own product, or a code sample. This is what separates a page worth citing from a page worth skipping.

  Evidence

  {
    "url": "https://vu1nz.com/faq",
    "words": 1044,
    "issues": [
      {
        "fix": "Add at least two things only you could publish: a real metric with its source, a named customer quote, a comparison table, a screenshot of your own product, or a code sample. This is what separates a page worth citing from a page worth skipping.",
        "key": "content.no_first_party_evidence",
        "count": 1,
        "label": "Almost no first-party evidence (1 signal of 6)",
        "samples": [
          "stat:true",
          "quote:false",
          "named-proof:false",
          "original-image:false",
          "code:false",
          "table:false"
        ],
        "dimension": "content"
      }
    ],
    "points": 5
  }

  P4
• warn

  /blog/protective-security-specialist-cicd-supply-chain — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/protective-security-specialist-cicd-supply-chain",
    "words": 3488,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/cyber-security-analyst-jobs-cicd-supply-chain-2026 — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/cyber-security-analyst-jobs-cicd-supply-chain-2026",
    "words": 3504,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/securitas-security-services-usa-cicd-security-architecture — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/securitas-security-services-usa-cicd-security-architecture",
    "words": 3509,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/security-systems-ci-cd-software-supply-chain — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-systems-ci-cd-software-supply-chain",
    "words": 3415,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/security-public-storage-cicd-workflow — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-public-storage-cicd-workflow",
    "words": 3771,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/vector-security-ci-cd-supply-chain — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/vector-security-ci-cd-supply-chain",
    "words": 3419,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/adt-security-ci-cd-automated-detection-triage — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/adt-security-ci-cd-automated-detection-triage",
    "words": 3341,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/trane-supply-ci-cd-supply-chain-security — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/trane-supply-ci-cd-supply-chain-security",
    "words": 3986,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/cyber-security-certifications-devsecops-architecture-guide — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/cyber-security-certifications-devsecops-architecture-guide",
    "words": 3625,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/identity-and-access-management-for-cloud-security — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/identity-and-access-management-for-cloud-security",
    "words": 3848,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/ai-agents-github-actions-security — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/ai-agents-github-actions-security",
    "words": 4033,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/adt-home-security-cicd-supply-chain-defense — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/adt-home-security-cicd-supply-chain-defense",
    "words": 3891,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/encrypted-messaging-github-actions-security — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/encrypted-messaging-github-actions-security",
    "words": 3821,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/security-service-ci-cd-supply-chain-defense — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-service-ci-cd-supply-chain-defense",
    "words": 3600,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/security-service-architecture-cicd-supply-chain — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/security-service-architecture-cicd-supply-chain",
    "words": 3716,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  /blog/screen-sharing-ci-cd-security — 1 issue (4 slop points)

  **Design: 3 of 3 images have no width/height — causes layout shift** Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.

  Evidence

  {
    "url": "https://vu1nz.com/blog/screen-sharing-ci-cd-security",
    "words": 2739,
    "issues": [
      {
        "fix": "Set explicit `width` and `height` (or an aspect-ratio box) on every image so the browser can reserve space before the file loads. This is the most common cause of content jumping as a page renders.",
        "key": "design.unsized_images",
        "count": 3,
        "label": "3 of 3 images have no width/height — causes layout shift",
        "dimension": "design"
      }
    ],
    "points": 4
  }

  P4
• warn

  Content — 4 pages open with an identical first sentence

  Write a page-specific opening for each. A shared intro means the first thing every crawler reads is the same, so nothing distinguishes the pages.

  Evidence

  {
    "count": 4,
    "weight": 4,
    "samples": [
      "\"skip to content you signed in with another tab or window rel…\" × 4"
    ],
    "dimension": "content"
  }

  P4
• warn

  Design — 9 distinct font families declared

  Cut to two or three typefaces (one display, one text, optionally one mono). Every extra family is another web font to download and another way the page looks unplanned.

  Evidence

  {
    "count": 9,
    "weight": 3,
    "samples": [
      "inter",
      "inter fallback",
      "jetbrains mono",
      "jetbrains mono fallback",
      "var(--font-sans)",
      "var(--font-mono)",
      "var(--default-font-family",
      "var(--default-mono-font-family",
      "var(--font-display)"
    ],
    "dimension": "design"
  }

  P4
• warn

  /compare — 1 issue (9 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (1×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.

  Evidence

  {
    "url": "https://vu1nz.com/compare",
    "words": 840,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 1,
        "label": "Unrendered {{template}} variable rendered on the page (1×)",
        "samples": [
          "{{ secrets.AWS_KEY }}"
        ],
        "dimension": "code"
      }
    ],
    "points": 9
  }

  P4
• warn

  / — 1 issue (9 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (1×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.

  Evidence

  {
    "url": "https://vu1nz.com/",
    "words": 1088,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 1,
        "label": "Unrendered {{template}} variable rendered on the page (1×)",
        "samples": [
          "{{ secrets.AWS_KEY }}"
        ],
        "dimension": "code"
      }
    ],
    "points": 9
  }

  P4
• warn

  /github-actions — 1 issue (9 slop points)

  **Code: Unrendered {{template}} variable rendered on the page (6×)** Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.

  Evidence

  {
    "url": "https://vu1nz.com/github-actions",
    "words": 654,
    "issues": [
      {
        "fix": "Trace the template or data binding that produced this and give it a fallback. Visible `undefined`/`{{var}}` text gets indexed verbatim and quoted back by answer engines.",
        "key": "code.leaked_value",
        "count": 6,
        "label": "Unrendered {{template}} variable rendered on the page (6×)",
        "samples": [
          "{{ secrets.GITHUB_TOKEN }}",
          "{{ secrets.VU1NZ_LICENSE }}",
          "{{ secrets.GITHUB_TOKEN }}",
          "{{ secrets.VU1NZ_LICENSE }}",
          "{{ secrets.ANTHROPIC_API_KEY }}"
        ],
        "dimension": "code"
      }
    ],
    "points": 9
  }

  P4
• warn

  /api/auth/github — 2 issues (8 slop points)

  **Content: Thin page — only 104 visible words** Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you. **Code: 4 placeholder hrefs (# / javascript:void)** Give every link real text or an aria-label, and point it at a real URL. `href="#"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.

  Evidence

  {
    "url": "https://vu1nz.com/api/auth/github",
    "words": 104,
    "issues": [
      {
        "fix": "Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you.",
        "key": "content.thin",
        "count": 104,
        "label": "Thin page — only 104 visible words",
        "dimension": "content"
      },
      {
        "fix": "Give every link real text or an aria-label, and point it at a real URL. `href=\"#\"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.",
        "key": "code.dead_links",
        "count": 4,
        "label": "4 placeholder hrefs (# / javascript:void)",
        "dimension": "code"
      }
    ],
    "points": 8
  }

  P4
• warn

  /api/auth/github?next=%2Fdashboard — 2 issues (8 slop points)

  **Content: Thin page — only 104 visible words** Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you. **Code: 4 placeholder hrefs (# / javascript:void)** Give every link real text or an aria-label, and point it at a real URL. `href="#"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.

  Evidence

  {
    "url": "https://vu1nz.com/api/auth/github?next=%2Fdashboard",
    "words": 104,
    "issues": [
      {
        "fix": "Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you.",
        "key": "content.thin",
        "count": 104,
        "label": "Thin page — only 104 visible words",
        "dimension": "content"
      },
      {
        "fix": "Give every link real text or an aria-label, and point it at a real URL. `href=\"#\"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.",
        "key": "code.dead_links",
        "count": 4,
        "label": "4 placeholder hrefs (# / javascript:void)",
        "dimension": "code"
      }
    ],
    "points": 8
  }

  P4
• warn

  /api/auth/github?next=%2Fapi%2Fgithub%2Fapp%2Finstall — 2 issues (8 slop points)

  **Content: Thin page — only 104 visible words** Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you. **Code: 4 placeholder hrefs (# / javascript:void)** Give every link real text or an aria-label, and point it at a real URL. `href="#"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.

  Evidence

  {
    "url": "https://vu1nz.com/api/auth/github?next=%2Fapi%2Fgithub%2Fapp%2Finstall",
    "words": 104,
    "issues": [
      {
        "fix": "Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you.",
        "key": "content.thin",
        "count": 104,
        "label": "Thin page — only 104 visible words",
        "dimension": "content"
      },
      {
        "fix": "Give every link real text or an aria-label, and point it at a real URL. `href=\"#\"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.",
        "key": "code.dead_links",
        "count": 4,
        "label": "4 placeholder hrefs (# / javascript:void)",
        "dimension": "code"
      }
    ],
    "points": 8
  }

  P4
• warn

  /api/auth/github?next=%2Fdashboard%2Fapi-keys — 2 issues (8 slop points)

  **Content: Thin page — only 104 visible words** Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you. **Code: 4 placeholder hrefs (# / javascript:void)** Give every link real text or an aria-label, and point it at a real URL. `href="#"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.

  Evidence

  {
    "url": "https://vu1nz.com/api/auth/github?next=%2Fdashboard%2Fapi-keys",
    "words": 104,
    "issues": [
      {
        "fix": "Either expand this to 300+ words of substantive content or remove it from the sitemap and internal nav. Thin pages dilute the crawl budget an answer engine spends on you.",
        "key": "content.thin",
        "count": 104,
        "label": "Thin page — only 104 visible words",
        "dimension": "content"
      },
      {
        "fix": "Give every link real text or an aria-label, and point it at a real URL. `href=\"#\"` navigation is invisible to crawlers and unusable with a keyboard or screen reader.",
        "key": "code.dead_links",
        "count": 4,
        "label": "4 placeholder hrefs (# / javascript:void)",
        "dimension": "code"
      }
    ],
    "points": 8
  }

  P4
• warn

  Crawl capped at 50 pages (50-page limit)

  The site has more pages than the 50-page budget for this scan, so pages beyond that were not analyzed. The score reflects what was crawled.

  Evidence

  {
    "urls": [
      "https://vu1nz.com/",
      "https://vu1nz.com/scanner",
      "https://vu1nz.com/pricing",
      "https://vu1nz.com/compare",
      "https://vu1nz.com/faq",
      "https://vu1nz.com/api",
      "https://vu1nz.com/github-actions",
      "https://vu1nz.com/mcp",
      "https://vu1nz.com/advisories",
      "https://vu1nz.com/free-scan",
      "https://vu1nz.com/blog",
      "https://vu1nz.com/blog/what-dependabot-misses",
      "https://vu1nz.com/blog/anatomy-of-shai-hulud-npm-worm",
      "https://vu1nz.com/blog/ship-safer-with-vu1nz-github-actions",
      "https://vu1nz.com/login",
      "https://vu1nz.com/register",
      "https://vu1nz.com/billing",
      "https://vu1nz.com/login?next=/api/github/app/install",
      "https://vu1nz.com/status",
      "https://vu1nz.com/login?next=/dashboard/api-keys",
      "https://vu1nz.com/blog/security-awareness-training-ci-cd-software-supply-chain",
      "https://vu1nz.com/blog/protective-security-specialist-cicd-supply-chain",
      "https://vu1nz.com/blog/cyber-security-analyst-jobs-cicd-supply-chain-2026",
      "https://vu1nz.com/blog/securitas-security-services-usa-cicd-security-architecture",
      "https://vu1nz.com/blog/vivint-security-ci-cd-supply-chain-defense",
      "https://vu1nz.com/blog/security-license-ci-cd-architecture",
      "https://vu1nz.com/blog/security-systems-ci-cd-software-supply-chain",
      "https://vu1nz.com/blog/security-public-storage-cicd-workflow",
      "https://vu1nz.com/blog/vector-security-ci-cd-supply-chain",
      "https://vu1nz.com/blog/adt-security-ci-cd-automated-detection-triage",
      "https://vu1nz.com/blog/cyber-security-certifications-devsecops-architecture-guide",
      "https://vu1nz.com/blog/identity-and-access-management-for-cloud-security",
      "https://vu1nz.com/blog/ai-agents-github-actions-security",
      "https://vu1nz.com/blog/adt-home-security-cicd-supply-chain-defense",
      "https://vu1nz.com/blog/encrypted-messaging-github-actions-security",
      "https://vu1nz.com/blog/security-service-ci-cd-supply-chain-defense",
      "https://vu1nz.com/blog/screen-sharing-ci-cd-security",
      "https://vu1nz.com/blog/security-service-architecture-cicd-supply-chain",
      "https://vu1nz.com/blog/security-testing-cicd-supply-chain-architecture",
      "https://vu1nz.com/blog/trane-supply-ci-cd-supply-chain-security",
      "https://vu1nz.com/blog/introducing-vu1nz-os",
      "https://vu1nz.com/blog/idor-testing-checklist",
      "https://vu1nz.com/blog/proof-based-xss-detection",
      "https://vu1nz.com/api/auth/github",
      "https://vu1nz.com/api/auth/github?next=%2Fdashboard",
      "https://vu1nz.com/api/auth/github?next=%2Fapi%2Fgithub%2Fapp%2Finstall",
      "https://vu1nz.com/api/auth/github?next=%2Fdashboard%2Fapi-keys",
      "https://vu1nz.com/password_reset",
      "https://vu1nz.com/join?return_to=%2Flogin%2Foauth%2Fauthorize%3Fclient_id%3DOv23liCgRRqa45vHR8Ae%26redirect_uri%3Dhttps%253A%252F%252Fvu1nz.com%252Fapi%252Fauth%252Fgithub%252Fcallback%26scope%3Dread%253Auser%2Buser%253Aemail%2Bread%253Aorg%26state%3D3c0908c7fd2bd5f12d819d6ab28ea4f5&source=oauth",
      "https://vu1nz.com/join?return_to=%2Flogin%2Foauth%2Fauthorize%3Fclient_id%3DOv23liCgRRqa45vHR8Ae%26redirect_uri%3Dhttps%253A%252F%252Fvu1nz.com%252Fapi%252Fauth%252Fgithub%252Fcallback%26scope%3Dread%253Auser%2Buser%253Aemail%2Bread%253Aorg%26state%3D45b149c98b434266804fec93882b12ca&source=oauth"
    ],
    "capped": true,
    "maxPages": 50,
    "stylesheets": [
      "https://vu1nz.com/_next/static/chunks/0kahss01duy6t.css"
    ],
    "pagesCrawled": 50
  }

  P5
• fail

  Slop Score: 72/100 — Sloppy

  Scanned 50 pages (79,613 words) and found 42 issues. Slop points by dimension — content 38, code 99, design 83. 0 is pristine, 100 is maximum slop. This measures observable defects — placeholder text, duplicate pages, leaked template variables, missing evidence, stale dates — not whether anything was written by AI.

  Evidence

  {
    "grade": "Sloppy",
    "score": 72,
    "totals": {
      "pages": 50,
      "words": 79613,
      "issues": 42
    },
    "byDimension": {
      "code": 99,
      "design": 83,
      "content": 38
    }
  }

  P5