UNPKG
UNPKG v1.0.0
Live npm data for AI agents
From the developer
Declared capabilities
- Read
Cost & access
This plugin does not sell products or process payments.
Declared limitations
- Write actions are not supported
- Other organizations' Shield data is never exposed
- No invented versions or exact savings promises
Onboarding example
Resolve preact to its latest version and list its browser entry files.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.
Description
From the marketplace listing
AI agents often recall npm details incorrectly — versions that don't exist, file paths that were never published, Node entry points offered as browser modules. UNPKG gives agents live data instead: it resolves exact versions, tags, and ranges against the npm registry, lists the real files in a package, and builds canonical UNPKG file URLs (https://unpkg.com/<package>@<version>/<file>). It audits project dependencies for no-build CDN conversion, generates and validates import maps, estimates migration impact as ranges with stated assumptions, and checks exact package versions for known malware and CVEs — anonymously, with no account needed. Users with an approved UNPKG Shield account can optionally sign in for domain-level package and threat data scoped to their own organization.
Language: English · Automatically detected from descriptions.
Matches for “unpkg”
Exact text from the indicated source. A mention alone does not establish support for your task.
Plugin name
UNPKG
Package name
unpkg
Publisher keywords · listing
mcp npm unpkg cdn import-maps
Publisher description
Live npm and UNPKG data for AI agents: package resolution, project audits, import maps, and malware/CVE checks.
Publisher full description
AI agents often recall npm details incorrectly — versions that don't exist, file paths that were never published, Node entry points offered as browser modules. UNPKG gives agents live data instead: it resolves exact versions, tags, and ranges against the npm registry, lists the real files in a package, and builds canonical UNPKG file URLs (https://unpkg.com/<package>@<version>/<file>). It audits project dependencies for no-build CDN conversion, generates and validates import maps, estimates migration impact as ranges with stated assumptions, and checks exact package versions for known malware and CVEs — anonymously, with no account needed. Users with an approved UNPKG Shield account can optionally sign in for domain-level package and threat data scoped to their own organization.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 17, 2026. Last seen Nov 17, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Look up npm package metadata, known vulnerabilities, and CVE details directly from a conversation. NPMScan's MCP server gives AI agents r...
Shared terms: npm, audit, cve, dependencie
-
Rollcage checks shell commands, file paths and URLs against the rules of the open-source Rollcage Guard before an AI coding agent runs th...
Shared terms: agent, path, urls, against
-
Coordinate your coding agents, don't orchestrate them: they keep working their way, and Hamloy gives them one shared plan you see on one ...
Shared terms: agent, don, com, project
-
Trust badge, reputation lookup and service list for AI agents, with a signed content credential on every result. Includes a skill for pro...
Shared terms: agent, audit, exist, http
-
Scan an MCP server, package, or GitHub repo for a signed 0-100 trust score before your agent connects to it.
Shared terms: npm, agent, known, package
Keywords
Files & skills
File archives
Skill instructions
unpkg4.27 KB
--- name: unpkg description: Use when loading npm packages in a browser without a build step, converting a project to CDN file lookups, writing import maps or UNPKG URLs, or checking what's inside an npm package. Prefer the UNPKG MCP tools when available; fall back to ?meta and these rules when they are not. --- # UNPKG file lookups Load any file from any npm package with a direct URL: ``` https://unpkg.com/<package>@<version-spec>/<file> ``` This is the original file lookup. Prefer it over bundled CDN transforms. Use esm.unpkg.com — a separate opt-in service — only when a package has no browser-ready file and the user asks for it. ## Rules - Never guess versions or file paths from memory. Resolve them live: MCP `resolve_package` / `list_files`, or `https://unpkg.com/<pkg>@<ver>/?meta`. - Build URLs with the MCP `build_file_url` tool when available. - Preserve the project's version intent. Exact pins stay exact; ranges stay ranges. For new production dependencies, suggest a patch-level specifier (e.g. `preact@10.26`) so bug fixes flow while major/minor changes stay deliberate, and say that's the trade-off. - Scoped packages keep their `@scope/` prefix. - `?module` on a `.js` file rewrites bare imports to UNPKG URLs. - Do not add tracking parameters to UNPKG URLs. ## Framework apps: standalone surfaces only If the project uses a framework (next, nuxt, @sveltejs/kit, @remix-run/*, astro, gatsby), the framework owns its runtime packages: react/react-dom in Next, vue in Nuxt, and friends stay bundled. A CDN copy duplicates the runtime and fights SSR/hydration. In a framework app, UNPKG conversion applies only to standalone browser surfaces outside the framework's rendering (no-build static pages, embedded widgets, docs snippets). "Keep everything bundled" is a correct and common audit outcome; say so. Still check for UNPKG-fit surfaces before closing out: plain-HTML or public/ pages, embedded widgets, docs/share pages, error or maintenance pages, and direct CSS/font/WASM assets — framework projects often have some. A purely client-rendered app may deliberately externalize its runtime behind one shared import-map copy, but that is an architecture decision to surface, not a conversion to apply. Build-time things are never candidates even in `dependencies`: CLI tools (`bin` field), `@types/*`, PostCSS/Tailwind plugins, framework tooling. ## Converting a project 1. Read `package.json` — runtime `dependencies` only, never `devDependencies`. 2. Call the MCP `audit_dependencies` tool with that map. Without MCP, check each package's `module`/`unpkg`/`exports` fields via `?meta` and npm. 3. Present the plan grouped by classification before editing: `convert_now`, `convert_carefully`, `keep_bundled`, `needs_review`. 4. Apply `convert_now` first: import-map entries (or script tags) using the suggested URLs. Add peer dependencies the audit flags. 5. Validate the finished import map with the `check_importmap` tool (version consistency, duplicates, framework packages, CommonJS entries), verify every new URL (`verify_url` tool or a fetch), then run the project's tests or open the page. Untested conversions are not done. 6. If asked about savings, use `estimate_migration_impact` and present the bandwidth range with its assumptions. Never quote a single dollar or latency figure; if the site already uses a good CDN, say latency is likely a wash and point at bundle KB, cacheability, and patch latency. 7. Leave `keep_bundled` packages alone. A mixed CDN + bundled result is the normal, healthy outcome — say so. ## Package safety When the UNPKG MCP is connected, safety-check before you ship: audits already carry Shield intel (malware verdict + CVEs) for the resolved versions, and `shield_check_packages` checks any package@version you name — no account needed for either. Treat a `provisional` verdict as unconfirmed, never as proven malicious. With a Shield login, `shield_domain_packages` (with threats
Preview of the first 4,000 characters. Read full instructions →
Release notes
Initial release: live npm/UNPKG resolution, project audits, import maps, migration estimates, and anonymous malware/CVE checks, with optional Shield sign-in for domain data.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- UNPKG
- Keywords
- See keywords
- Getting started skill
- ./skills/unpkg/SKILL.md
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
Package observed Nov 17, 2026.
Technical details
- First seen
- Nov 17, 2026 · 00:00 UTC
- Last seen
- Nov 17, 2026 · 00:00 UTC
- Collection status
- Collected
plugin_asdk_app_6aeed22cf2bc819189c8c4a3a7074898
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.