— No reviews yet
0 installs
2 views
0.0% view→install
Install
$ agentstack add skill-alizharb-agent-skills-debug-composer-conflicts ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Debug Composer Conflicts? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
Debug Composer Conflicts
Workflow
- Run
composer why-notor inspect Composer's solver output. - Check PHP version, Laravel version, package constraints, minimum stability, and plugin allowances.
- Confirm whether security advisories are blocking a version.
- Prefer updating constraints honestly over forcing ignored advisories.
- Update docs and CI matrix when support changes.
- Re-run
composer update --dry-runor the intended install/update command.
Verification
composer validatepasses.- The intended
composer requireorcomposer updatesucceeds.
Common Mistakes
- Pinning an old vulnerable framework version.
- Adding broad constraints without testing each supported lane.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AlizHarb
- Source: AlizHarb/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.