Skip to content
Back to search

vercel-labs

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 16 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/vercel-labs/nostics with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/vercel-labs/nostics'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vercel-labs--logs-sdk/badge.svg)](/listings/vercel-labs--logs-sdk)

HTML

<a href="/listings/vercel-labs--logs-sdk"><img src="/api/listings/vercel-labs--logs-sdk/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

pnpm add nostics

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 18 lines
  1. {
  2. "name": "vercel-labs",
  3. "owner": {
  4. "name": "Eduardo San Martin Morote"
  5. },
  6. "plugins": [
  7. {
  8. "name": "nostics",
  9. "source": "./",
  10. "description": "Claude Code plugin for nostics: structured diagnostic codes for JavaScript/TypeScript libraries and frameworks",
  11. "version": "1.4.0",
  12. "author": {
  13. "name": "Eduardo San Martin Morote"
  14. },
  15. "skills": ["./skills/nostics", "./skills/add-diagnostic"]
  16. }
  17. ]
  18. }
README.md · README · 142 lines
  1. <p align="center">
  2. <img src="./docs/public/nostics.svg" alt="nostics" width="320">
  3. </p>
  4. # nostics
  5. [![npm version](https://img.shields.io/npm/v/nostics?color=blue)](https://npmx.dev/nostics)
  6. [![npm downloads](https://img.shields.io/npm/dw/nostics?color=blue)](https://npmx.dev/nostics)
  7. [![CI](https://img.shields.io/github/actions/workflow/status/vercel-labs/nostics/ci.yml?branch=main&label=CI)](https://github.com/vercel-labs/nostics/actions/workflows/ci.yml)
  8. [![bundle size](https://deno.bundlejs.com/badge?q=nostics&treeshake=[{+defineDiagnostics+}])](https://bundlejs.com/?q=nostics&treeshake=%5B%7B+defineDiagnostics+%7D%5D)
  9. Errors worth reading.
  10. `nostics` helps you replace ad hoc error strings with stable diagnostic codes, actionable fixes, source locations, and docs links.
  11. ```txt
  12. [NUXT_B2011] Plugin `./runtime/analytics.server.ts` is server-only but was registered with mode `client`.
  13. ├▶ fix: Rename the file or register it with mode `server`.
  14. ├▶ sources: modules/analytics.ts:18:5
  15. ╰▶ see: https://nuxt.com/e/b2011
  16. ```
  17. ## Install
  18. ```bash
  19. pnpm add nostics
  20. ```
  21. ## Quick start
  22. ```ts
  23. import { createConsoleReporter, defineDiagnostics } from 'nostics'
  24. export const diagnostics = defineDiagnostics({
  25. docsBase: (code) => `https://nuxt.com/e/${code.replace('NUXT_', '').toLowerCase()}`,
  26. reporters: [createConsoleReporter()],
  27. codes: {
  28. NUXT_B2011: {
  29. why: (p: { src: string; mode: 'client' | 'server' }) => {
  30. const expected = p.mode === 'client' ? 'server' : 'client'
  31. return `Plugin "${p.src}" is ${expected}-only but was registered with mode "${p.mode}".`
  32. },
  33. fix: (p: { mode: 'client' | 'server' }) => {
  34. const expected = p.mode === 'client' ? 'server' : 'client'
  35. return `Rename the file or register it with mode "${expected}".`
  36. },
  37. },
  38. NUXT_B5001: {
  39. why: (p: { value: string; configPath: string }) =>
  40. `Invalid compatibilityDate "${p.value}" in ${p.configPath}.`,
  41. fix: (p: { example: string }) => `Use an ISO date like "${p.example}", or "latest".`,
  42. },
  43. },
  44. })
  45. ```
  46. Use the generated handles where the problem happens:
  47. ```ts
  48. const plugin = resolvePlugin()
  49. const source = locatePluginCall(plugin)
  50. const config = loadNuxtConfig()
  51. diagnostics.NUXT_B2011({
  52. src: plugin.src,
  53. mode: plugin.mode,
  54. sources: [source],
  55. })
  56. throw diagnostics.NUXT_B5001({
  57. configPath: config.filepath,
  58. value: config.compatibilityDate,
  59. example: '2024-04-03',
  60. })
  61. ```
  62. Calling a handle reports the diagnostic and returns a `Diagnostic`. Throwing the return value raises it. The params are inferred from your `why` and `fix` functions.
  63. ## Claude Code plugin
  64. Install the plugin to give Claude skills for your diagnostic catalog:
  65. ```bash
  66. claude plugin add https://github.com/vercel-labs/nostics
  67. ```
  68. Claude will automatically pick up the `nostics` API reference and an `add-diagnostic` skill that finds the right catalog, chooses the next free code, and wires the call site.
  69. ## Agent skills
  70. Prefer just the skills, without the plugin? Install them with [`npx skills`](https://github.com/vercel-labs/skills) into any supported agent (Claude Code, Codex, Cursor, opencode, and more):
  71. ```bash
  72. npx skills add vercel-labs/nostics
  73. ```
  74. ## Why use it
  75. - Stable codes that users can search and docs can link to.
  76. - Typed params at the call site.
  77. - `Diagnostic` instances that extend `Error`.
  78. - Built-in console, file, fetch, and Vite dev reporters.
  79. - Plain, ANSI, and JSON formatters.
  80. - A build plugin that strips report-only diagnostics from production bundles.
  81. The structured shape also makes diagnostics easier for tools and coding agents to read, without making that the main workflow.
  82. ## Vite plugins
  83. Build-time plugins live in the separate [`@nostics/unplugin`](./packages/unplugin) package:
  84. ```bash
  85. pnpm add -D @nostics/unplugin
  86. ```
  87. For library builds, use the strip plugin:
  88. ```ts
  89. import { nosticsStrip } from '@nostics/unplugin/strip-transform'
  90. export default defineConfig({
  91. plugins: [nosticsStrip.vite()],
  92. })
  93. ```
  94. For browser diagnostics during Vite dev, use `createDevReporter()` in the browser and `nosticsCollector` in the consuming app:
  95. ```ts
  96. import { nosticsCollector } from '@nostics/unplugin/dev-server-collector'
  97. export default defineConfig({
  98. plugins: [nosticsCollector.vite()],
  99. })
  100. ```
  101. ## Docs
  102. See the docs site for the guide, production build notes, dev collector setup, and API reference.
  103. ## License
  104. [MIT](./LICENSE)
install.sh · Bundled script · 34 lines · 1 finding marked
  1. #!/usr/bin/env bash
  2. #
  3. # nostics Claude Code Plugin Installer
  4. #
  5. # Adds the repo as a marketplace and installs the plugin project-scoped.
  6. # Run from your project root — the plugin is scoped to $PWD.
  7. #
  8. # Usage: gh api repos/vercel-labs/nostics/contents/install.sh --jq '.content' | base64 -d | bash
    • Note: Runs a script fetched from GitHub's contents API (base64-decoded into a shell)
    • Line 8 on GitHub
  9. #
  10. set -e
  11. PLUGIN_NAME="nostics"
  12. MARKETPLACE_NAME="vercel-labs"
  13. REPO="vercel-labs/nostics"
  14. echo "nostics Claude Code Plugin Installer"
  15. echo ""
  16. # Add the marketplace (skip if already registered)
  17. if claude plugin marketplace list 2>/dev/null | grep -q " $MARKETPLACE_NAME$"; then
  18. echo "-> Updating marketplace..."
  19. claude plugin marketplace update "$MARKETPLACE_NAME"
  20. else
  21. echo "-> Adding marketplace..."
  22. claude plugin marketplace add "$REPO" --scope project
  23. fi
  24. # Install the plugin project-scoped (auto-enables)
  25. echo "-> Installing plugin..."
  26. claude plugin install "${PLUGIN_NAME}@${MARKETPLACE_NAME}" --scope project
  27. echo ""
  28. echo "Installed successfully! Restart Claude Code for the plugin to take effect."

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.