Simulate and detect software supply chain attacks including typosquatting detection via Levenshtein distance, dependency confusion testing against private registries, package hash verification with pip, and known vulnerability scanning with pip-audit.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionperforming-supply-chain-attack-simulationExecute the skills CLI command in your project's root directory to begin installation:
Fetches performing-supply-chain-attack-simulation from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate performing-supply-chain-attack-simulation. Access via /performing-supply-chain-attack-simulation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| name | performing-supply-chain-attack-simulation |
| description | Simulate and detect software supply chain attacks including typosquatting detection via Levenshtein distance, dependency confusion testing against private registries, package hash verification with pip, and known vulnerability scanning with pip-audit. |
| domain | cybersecurity |
| subdomain | application-security |
| tags | - supply-chain - typosquatting - dependency-confusion - package-verification - pip-audit - PyPI - software-composition-analysis |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | - PR.PS-01 - PR.PS-04 - ID.RA-01 - PR.DS-10 |
Software supply chain attacks exploit trust in package registries through typosquatting (registering names similar to popular packages), dependency confusion (publishing higher-version public packages matching private names), and compromised package distribution. This skill detects these attack vectors by computing Levenshtein distance between package names and popular PyPI packages, verifying package integrity via SHA-256 hash comparison, scanning for known CVEs with pip-audit, and testing dependency resolution order for confusion vulnerabilities.
pip-audit, Levenshtein, requestsLegal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.
JSON report with risk scores per package, detected attack vectors, hash verification results, and CVE findings.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
Solid pick for teams standardizing on skills: performing-supply-chain-attack-simulation is focused, and the summary matches what you get after install.
Registry listing for performing-supply-chain-attack-simulation matched our evaluation — installs cleanly and behaves as described in the markdown.
performing-supply-chain-attack-simulation reduced setup friction for our internal harness; good balance of opinion and flexibility.
performing-supply-chain-attack-simulation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added performing-supply-chain-attack-simulation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in performing-supply-chain-attack-simulation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added performing-supply-chain-attack-simulation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
performing-supply-chain-attack-simulation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend performing-supply-chain-attack-simulation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: performing-supply-chain-attack-simulation is focused, and the summary matches what you get after install.
showing 1-10 of 59