Dependency Analyzer
Audit package.json dependencies, ranges and risk flags in seconds
Runs 100% in your browser — nothing is ever uploaded.
What is Dependency Analyzer?
Paste your project's package.json and get an instant dependency audit: totals per section (dependencies, devDependencies, peer, optional), how many versions are pinned exactly versus floating with ^ or ~, wildcard and git/URL dependencies that undermine reproducible builds, packages listed in multiple sections, and risky patterns. Your manifest is analyzed locally — nothing is uploaded.
How to use Dependency Analyzer
- Paste the full package.json content into the input.
- Click Analyze to parse the manifest.
- Review the summary grid: counts, pinned vs range, risky specifiers.
- Check the per-package table and fix flagged entries in your project.
Frequently asked questions
What risk flags does the analyzer raise?
Wildcard versions (* or x), latest tags, git and http(s) URL dependencies, file: links, packages that appear in both dependencies and devDependencies, and pre-1.0.0 packages where ^ still allows breaking minor bumps.
Does it fetch data from the npm registry?
No — analysis is purely static on the JSON you paste, which keeps it instant and private. It reasons about version ranges and structure, not about the latest published versions.
Is my package.json shared with anyone?
No. Parsing happens in your browser only. Internal package names and private registry references never leave your machine.
Do these tools touch my servers?
No. OpsForge tools are pure calculators and generators that run in your browser — they never connect to your infrastructure. You copy the result and apply it yourself.
Is the chmod calculator accurate for all systems?
Yes — octal permission notation is a POSIX standard, so the results apply identically on Linux, macOS and BSD.
Will more DevOps tools be added?
Yes — Dockerfile, docker-compose, nginx and CI config generators are on the roadmap. Everything will stay free and client-side.