How to Use GitHub malware advisories in Cursor
Fetch malicious-package advisories with affected packages, version ranges, references, and publication dates. Use them to check reported package threats; GitHub treats malware separately from ordinary vulnerabilities.
Prompts to try with GitHub malware advisories in Cursor
Copy an example into Cursor, or ask in your own words.
Use GitHub malware advisories to check npm packages express, lodash, and axios, then compare any reported affected ranges with this project's lockfile.
Use GitHub malware advisories to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from GitHub malware advisories and tell me what changed since last week.
Check GitHub malware advisories and summarize what you find in three bullet points.
Pull the newest data from GitHub malware advisories and give me the result as a table.
How to set up GitHub malware advisories in Cursor
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
Use Add to Cursor on the console's Agents & MCP page, or add this to .cursor/mcp.json (one project) or ~/.cursor/mcp.json (every project):
{ "mcpServers": { "spiral": { "url": "https://api.spiral.ai/mcp" } } } - Sign in
Open Cursor Settings › MCP, click Connect next to spiral, sign in to Spiral and click Authorize. No API key. Spiral then shows as connected, with its tools listed.
Use the Spiral skill
- Send Cursor this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run GitHub malware advisories
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "github-com/repositories/malware_advisories", "input": { "cursor": "<cursor>" } }'
Then paste one of the prompts above: Cursor finds GitHub malware advisories on Spiral, shows the price and runs it.
GitHub malware advisories providers and prices
Spiral runs GitHub malware advisories through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Cursor for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Per page | 1 to 100 | 30 | per_page |
| Direction | asc or desc | desc | direction |
| Ecosystem | rubygems, npm, pip, maven, nuget, composer, go, rust and 5 more | Package ecosystem. pip is PyPI, rust is crates.io, composer is Packagist, actions is GitHub Actions. |
Every API field of GitHub · Malware advisories is on its tool page: open its card above.
What can you do with GitHub malware advisories in Cursor?
Build a dependency review beside the code using GitHub files, release notes, issue evidence, and package advisories. A coding agent can compare those records with the project's manifests and turn the findings into proposed changes.
Review a dependency before adoption
Build an adoption brief covering repository status, contribution concentration, license text, issue categories and totals, release history, and reported vulnerability or malware concerns for the exact packages under consideration.
Prepare a dependency upgrade review
Compare the installed version with published releases, read migration files and known issue reports, and check relevant advisories. Include project status and contribution concentration when deciding how much upstream support to expect.
Investigate a reported package incident
Read the advisory and affected package ranges, compare release notes and manifests, then inspect related issue categories, reports, and totals. Keep a documented vulnerability fix separate from a malicious-package report.
Maintain a package security watch
Check a defined package list for malware reports and known advisory changes, then compare repository status, manifests, and published releases with the previous review. Produce a change report with links to the supporting records.
Write a vulnerability remediation brief
Explain a known CVE using its affected ranges, upstream files, and release notes. Check malicious-package reports separately and identify whether the evidence supports an upgrade or removing the package.
More on GitHub malware advisories and Cursor
Overview
GitHub malware advisories in other agents
Questions about GitHub malware advisories in Cursor
Can Cursor use GitHub malware advisories?
Yes. Add Spiral to Cursor as an MCP server, and Cursor can find and run GitHub malware advisories like any built-in tool.
How much does GitHub malware advisories cost in Cursor?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Cursor plan is separate.
Do I need an Alexandria account to use GitHub malware advisories in Cursor?
No. Spiral runs GitHub malware advisories on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up GitHub malware advisories in Cursor?
About two minutes: add the hosted server, then sign in.
Does Cursor wait while GitHub malware advisories runs?
GitHub malware advisories runs in the background. Cursor starts the run, checks on it and gives you the json when it's ready.
Can I reuse anything that is public on GitHub?
Public visibility alone does not grant unrestricted reuse. GitHub says that without a license, default copyright restrictions apply to source code; its Advisory Database has a separate CC BY 4.0 license.
How current is GitHub's data?
Freshness depends on the record. Contributor results can be a few hours old because GitHub caches them, while a file selected by branch can change whenever new commits arrive.
Does a GitHub release history include every version tag?
No. GitHub excludes Git tags that have no associated release, and its latest-release lookup excludes prereleases and drafts.
Do GitHub issues include pull requests?
GitHub's underlying issue responses can contain both, with pull requests identified separately. An issue-only backlog should exclude pull requests before its totals are compared.
Where do GitHub's malware reports come from?
GitHub automatically publishes malware advisories from the npm security team and the OpenSSF Malicious Packages repository. These reports concern malicious packages and are separate from ordinary vulnerability advisories.
Start using GitHub malware advisories in Cursor
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Cursor:
set up https://spiral.ai/SKILL.md


