agentleFS
Sign inStart free
ecosyste-msecosyste-ms/claude-plugin/skills/advisories/SKILL.md

advisories

Skill3 starsChanged 6 months agoMITView on GitHub

Query advisories.ecosyste.ms for security vulnerability metadata aggregated from GitHub Security Advisories, OSV, RustSec, ErlEf and others. Use when checking a package or repo for known CVEs, listing recent advisories for an ecosystem, or fetching CVSS/EPSS scores and patched version ranges.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. ecosyste-ms/skills★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All responses are JSON. No auth required.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ecosyste.ms Advisories API

Base URL: https://advisories.ecosyste.ms/api/v1

All responses are JSON. No auth required. Set a User-Agent header. Results are deduplicated by CVE across sources.

Full OpenAPI spec: https://advisories.ecosyste.ms/docs/api/v1/openapi.yaml

Look up advisories for a package or repo

By purl (include a version to get only advisories affecting that version) or by source repository URL:

curl -s 'https://advisories.ecosyste.ms/api/v1/advisories/lookup?purl=pkg:npm/lodash@4.17.20'
curl -s 'https://advisories.ecosyste.ms/api/v1/advisories/lookup?repository_url=https://github.com/rails/rails'

List and filter advisories

# all advisories for a package
curl -s 'https://advisories.ecosyste.ms/api/v1/advisories?ecosystem=pypi&package_name=django'

# critical severity only, newest first
curl -s 'https://advisories.ecosyste.ms/api/v1/advisories?ecosystem=npm&severity=CRITICAL&sort=published_at&order=desc'

# everything published since a date
curl -s 'https://advisories.ecosyste.ms/api/v1/advisories?created_after=2026-01-01T00:00:00Z'

Filters: ecosystem, package_name, severity (LOW/MODERATE/HIGH/CRITICAL), repository_url, source, created_after, updated_after, sort, order, page, per_page.

Single advisory

curl -s 'https://advisories.ecosyste.ms/api/v1/advisories/GHSA-jf85-cpcp-j695'

Sources

curl -s 'https://advisories.ecosyste.ms/api/v1/sources'

Response fields

uuid, title, description, severity, cvss_score, cvss_vector, epss_percentage, epss_percentile, published_at, withdrawn_at, identifiers (CVE/GHSA ids), references, repository_url, blast_radius, source_kind, packages[] (each with ecosystem, package_name, purl, versions[].vulnerable_version_range, versions[].first_patched_version, affected_versions, unaffected_versions).

When to use

  • Checking whether a specific package@version has known vulnerabilities
  • Auditing a project's dependency list against known CVEs
  • Finding the first patched version for an advisory
  • Tracking new advisories published for an ecosystem since a given date

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free