- Home
- Skills
- APIs & Backend
- Dependency reality check
Dependency reality check
Verify software dependency existence, API support, and environment compatibility before adoption.
Free
Works with the AI Agents you already use
Dependency reality check
Example session with this skill installed
I want to add lodash-es@4.17.21 to my React project. Can you verify if this is the right version for an ESM-only environment and if it conflicts with my existing package.json?
- Read your context and instructions
- Compiled the dependency reality check
I have assessed the proposed addition of lodash-es@4.17.21 against your project environment. The package was verified via the npm registry and compared against your local manifest.
Dependency Assessment Report: lodash-es
| Category | Detail | Result |
|---|---|---|
| Package/Version | lodash-es @ 4.17.21 | Verified |
| Registry | npm (authoritative) | Found |
| Upstream Source | github.com/lodash/lodash | Confirmed |
| API Support | ESM Exports | Validated for v4.17.21 |
| Compatibility | Peer deps & Runtime | Concern Found |
| Redundancy | Existing Tools | Potential Overlap |
Verdict: Conditional Concern
Findings:
1.
Identity: lodash-es is the official ESM build of Lodash. Version 4.17.21 is the current stable release. No typosquatting detected.
2.
Environment: Your package.json specifies "type": "module". lodash-es is natively compatible. However, your lockfile shows lodash (CJS) is already a transitive dependency of formik. Adding lodash-es will increase bundle size by duplicating logic.
3.
API Validation: The 4.17.21 docs confirm all requested utility functions are exported as individual modules, fitting your tree-shaking requirements.
4.
Standard Library: Note that Array.prototype.flat and Object.assign in your target Node 20 environment may replace the need for _.flatten and _.assign.
Next steps
- Review if native JavaScript methods can replace your specific Lodash use cases to avoid the extra 25kB gzipped.
- If you proceed, use an alias or deduplication strategy to handle the existing CJS
lodashdependency. - Run
npm list lodashto see the full dependency tree impact before installing.
Connects securely to your tools. The creator never sees your data.
About this skill
Supply-chain attacks and dependency bloat often stem from poor vetting. This skill systematically verifies software packages before you add them to your package.json or requirements.txt, ensuring they exist, support your required APIs, and fit your environment.
What it does
- Identity verification checks the authoritative registry for exact names and versions to prevent typosquatting.
- API validation confirms the intended functions and behaviors exist in the specific version requested.
- Environment auditing compares runtime ranges and peer dependencies against your project manifest and lockfiles.
- Overlap detection identifies if your current dependencies or standard library already provide the required capability.
- Conflict resolution flags version mismatches between the proposed package and the locked project environment.
How it works
- Identify the exact package, registry, and version range you are considering.
- Consult authoritative registry records and upstream documentation to verify the package identity.
- Inspect project files like
package-lock.jsonorpoetry.lockto map out compatibility constraints. - Compare the intended use case against the library's actual versioned API.
- Report a dated verdict with evidence, naming any gaps or material concerns found.
Frameworks & tools
This skill works with major registries like npm, PyPI, and RubyGems. It analyzes manifests and lockfiles including package.json, requirements.txt, composer.json, and environment-specific declarations.
Why this beats prompting it yourself
Standard LLMs often hallucinate package names or mix up API signatures between versions. This skill enforces a strict verification workflow that prioritizes authoritative registry data over probabilistic generation and forces an environment-wide compatibility check that users often overlook.
Use cases
- Vetting a new library for a production microservice to avoid breaking changes.
- Diagnosing why a proposed dependency version is rejected by your current lockfile.
- Checking for "lookalike" package names during a security-conscious onboarding.
- Auditing existing projects to replace redundant libraries with standard features.
Known limitations
This is not a security audit or authenticity certification. It cannot prove a package is safe or well-maintained, only that it matches the registry and technical requirements.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Registry timeouts are reported as unavailable, not nonexistent. Does not certify security or maintenance status. Manual authorization required for edits.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 16 days ago
- Free with an Agensi account