Score breakdown0 Version history1 Source
Category Weight Category score Contribution
Security prompt, exec, net, exfil, eval
35%
100
35.0 pts
Supply chain hash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenance staleness, pinning, CI
15%
100
15.0 pts
Transparency SKILL.md, perms, README
15%
100
15.0 pts
Community installs, verify, response
15%
100
15.0 pts
Findings & checks · 0 flagged
Security score 100 · 0 findings
✓ — All security checks passedNo findings in this category for the latest scan. pass
Supply chain score 100 · 0 findings
✓ — All supply chain checks passedNo findings in this category for the latest scan. pass
Maintenance score 100 · 0 findings
✓ — All maintenance checks passedNo findings in this category for the latest scan. pass
Transparency score 100 · 0 findings
✓ — All transparency checks passedNo findings in this category for the latest scan. pass
Community score 100 · 0 findings
✓ — All community checks passedNo findings in this category for the latest scan. pass
Every scanned point with the score it earned and what moved between them.
1 scans · 90 days d79592e latest
Jun 24, 2026 100 d79592e
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
skills/frontend/nextjs/SKILL.md · 1 file skills/frontend/nextjs/SKILL.md 1.9 KB · Markdown Rendered Raw ⧉ Copy
Next.js 15 (App Router) PUDO Checklist 1. PLAN (Architecture & Strategy) [ ] Rendering Strategy: Define which routes will be Server Components (RSC) and which require Client Components (use client). [ ] Data Fetching: Plan caching strategies using Next.js 15's native fetch overrides and React.cache. [ ] Routing Tree: Map out nested layouts, loading.tsx, error.tsx, and not-found.tsx boundaries. [ ] Mutations: Plan Server Actions for data mutations instead of traditional API routes where possible. 2. UNDERSTAND (Context & Auditing) [ ] RSC Boundary: Ensure use client directives are pushed as far down the component tree as possible. [ ] Bundle Analysis: Audit third-party packages to ensure they are compatible with Server Components. [ ] State Management: Review where global state (Zustand, Redux) is truly needed versus URL state or server state. 3. DEVELOP (Implementation) [ ] Components: Build Server Components by default. Extract interactivity (hooks, events) into minimal Client Components. [ ] Forms & Mutations: Use React 19 hooks (useActionState, useFormStatus) combined with Server Actions. [ ] Streaming: Wrap slow data-fetching components in <Suspense> to stream HTML to the client progressively. [ ] Assets: Utilize <Image>, <Link>, and next/font for automatic asset optimization. [ ] Caching: Verify Data Cache, Full Route Cache, and Router Cache behaviors. Configure revalidate tags correctly. [ ] SEO & Metadata: Implement dynamic generateMetadata for accurate Open Graph and SEO tags. [ ] Web Vitals: Check LCP (Largest Contentful Paint) and CLS (Cumulative Layout Shift) metrics. [ ] Edge Compatibility: Ensure middleware and essential handlers are Edge-runtime compatible if deploying to Vercel/similar.