Skip to main content
All five tools are available as MCP tools and as subcommands under npx githits@latest pkg.
The Package Intelligence tools support 13 registries: npm, PyPI, Hex, Crates, vcpkg, Zig, NuGet, Maven, Packagist, RubyGems, Go, Swift, and Pub. Dependency data supports all 13 registries. Vulnerability data is unavailable for vcpkg and Zig.
From CLI and MCP 0.38.0, pub: targets select Dart and Flutter packages from Pub, such as pub:http or pub:http@1.2.2. All five Package Intelligence tools accept Pub targets; pkg_info requires an unversioned target. Package names keep their native case, and exact versions keep build metadata. Dependency output can show SDK graph namespaces such as flutter_sdk next to a package or importer. These identify the dependency’s source in the graph and cannot be passed as target registries. Hosted MCP availability depends on the deployed package version. From CLI and MCP 0.32.0, cargo: is an input alias for public crates.io crates: targets. Structured registry inputs also accept cargo. For example, cargo:serde and crates:serde select the same package; canonical registry identities remain crates. Hosted MCP receives this support after adoption and deployment of that package version.
pkg_info returns a quick triage summary for any package: the default selected release and its publish date, license, repository popularity, download volume, and vulnerability status. The vulnerability summary keeps two counts separate: advisories that affect the selected release, and package-wide advisory history across all versions. Pass verbose: true to add GitHub language breakdown, topics, last-pushed date, published-version count, download refresh date, package-wide advisory history, and recent changes.CLI usage
Parameters
string
required
Unversioned package target in registry:name form, for example npm:express or npm:@types/node. Scoped names are supported. Registries: npm, pypi, hex, crates, vcpkg, zig, nuget, maven, packagist, rubygems, go, swift, or pub. pkg_info describes the default selected release, so omit any @version pin; supplying one is rejected.
boolean
When true, adds GitHub language/topics/last-pushed, published-version count, download refresh date, package-wide advisory history (all versions), and recent changes to the text output. Has no effect when format: "json" is set.
Example
Returns, when available: selected version, license, description, GitHub stars/forks/open issues, monthly or total downloads, publish age, and a compact vulnerability status line with separate selected-release and package-wide advisory counts.From CLI and MCP 0.39.0, the overview describes the default selected release, which can differ from the registry’s latest pointer. When GitHits skips that pointer, the output explains why: the release may be deprecated, yanked, unlisted, have no files, or be a prerelease. The vulnerability line then uses Selected: instead of Latest:. Some packages have no default release; the selected version is omitted. For a prerelease-only package, the output explains that installation requires an explicit version. Hosted MCP gets this behavior after the released package is adopted and deployed.JSON output includes version and publishedAt for the selected release, latestVersion and latestVersionPublishedAt for the registry’s latest pointer, and registryLatestDifference: {version, reason} when the two differ. reason is one of DEPRECATED, YANKED, NO_FILES, UNLISTED, or PRERELEASE_EXCLUDED. version is omitted when no release is selected. JSON also includes versionCount (published versions), downloads.refreshedAt (download data freshness), and advisoryHistory.total (package-wide advisory count). The vulnerabilities.affectsLatest key keeps its name but describes the selected release. To list the historical advisories themselves, use pkg_vulns with advisory_scope: "all".From CLI and MCP 0.33.0, package info can show a Package registry row naming the registry repository that supplied the metadata, such as Google Maven. This is separate from the package’s source-code repository. pkg_info, pkg_deps, and pkg_vulns JSON include registryRepository: {id, name, url} when that registry is known; otherwise the row and field are omitted. Hosted MCP availability depends on the deployed package version.
pkg_vulns fetches CVE and OSV security advisories for a package or a specific pinned version. It returns a count summary, each advisory with its OSV ID, severity, affected version ranges, and fix versions. Malicious-package advisories appear in a separate bucket.Reports distinguish affected, non-affecting, and unknown assessments. From CLI and MCP 0.31.0, use advisory_scope: "unknown" (CLI --scope unknown) to inspect advisories that could not be evaluated and the reasons why. advisory_scope: "all" includes every outcome. A historical advisory does not mean the inspected version is affected, and an unknown assessment does not establish that it is unaffected.By default the tool checks only the inspected package. Pass include_transitive: true (CLI --transitive) for an npm-audit-style audit that also reports vulnerabilities in the versions resolved by the dependency graph. Transitive audits are opt-in because they add graph-analysis cost.CLI usage
Parameters
string
required
Package target in registry:name[@version] form, for example npm:lodash@4.17.20. Omit the version to check the latest release. Scoped names are supported. Go module versions are accepted with or without the leading v (1.24.0 or v1.24.0); other registries reject tag-style v-prefixed inputs except Swift. Vulnerability data is unavailable for vcpkg and Zig.
string
Filter to advisories at or above this level: low, medium, high, or critical. Omit to include all advisories, including those with no assigned severity. Applies to both direct and transitive rows.
boolean
When true, includes retracted advisories. Defaults to false. Affects direct package rows only; transitive withdrawn advisories remain excluded.
boolean
When true, audits vulnerabilities in the versions resolved by the dependency graph in addition to the inspected package. Defaults to false because the audit adds graph-analysis cost. In the CLI, use --transitive.
string
Which advisory rows to return: affected (default), non_affecting (confirmed not to affect the inspected version), unknown (could not be evaluated), or all (every outcome). Counts cover affected, non-affecting, unknown, and all advisories regardless of the selected scope. Applies to both direct and transitive rows.
boolean
When true, shows every selected advisory assessment and expands its fields in text output. format: "json" always returns the complete structured assessment envelope. Full source reports require details: true in either format.
boolean
From 0.40.0, includes full advisory text and source metadata from OSV for every selected direct advisory. Adds live source reads and can produce long output. Defaults to false. In the CLI, use --details.
Example
Returns: a severity-filtered advisory list with OSV IDs, matched affected ranges, and candidate fix versions when available. Candidate fixes are source-reported and do not establish release availability or a safe upgrade.Unknown assessments appear in direct reports and opt-in transitive audits, including dependency packages with only unknown assessments. Transitive audits inspect the resolved package graph, not your application’s lockfile.JSON retains explicit unknown assessment statuses and nonempty reasons. Do not interpret affectsInspectedVersion: false or affectsResolvedVersion: false as a confirmed negative when the assessment status is unknown. The direct summary’s total remains the affected count; use the separate affected, non-affecting, unknown, and all counts to assess coverage. Unsupported or incomplete assessments are not evidence of no vulnerabilities.
Default MCP text output caps advisory rows. Use verbose: true to see every selected advisory. CLI text shows every selected direct and transitive row; --verbose expands assessment fields without changing the row count. Use MCP format: "json" or CLI --json for the complete structured assessment envelope. These options alone do not request source reports.
Full advisory reportsFrom CLI and MCP 0.40.0, details: true (CLI --details) adds full OSV advisory text and source metadata after the assessment groups. Source reports cover every selected direct advisory, even when MCP caps the displayed assessment rows. The report bodies are untruncated in text and JSON; JSON includes them in sourceDetails.Source failures preserve the package assessments and include per-source diagnostics. The CLI exits nonzero if a source report fails. Source text does not recompute affectedness or establish a safe upgrade. Hosted MCP requires adoption and deployment of the released package.For a dependency’s report, call pkg_vulns on its registry:name@resolvedVersion with details: true, or use the CLI advisory lookup below with --verbose.Look up an advisory ID instead (CLI only)From 0.39.0, npx githits@latest vulns <ids...> starts from CVE, OSV, or GHSA IDs instead of a package. It shows the packages each advisory affects, normalized affected ranges, the reported CVSS score, and source-reported fixes. Partial outcomes and recovery actions appear explicitly. pkg vulns assesses whether a specific installed version is affected; vulns does not. MCP has no equivalent tool.
--verbose adds the full source report, including OSV schema, related and upstream IDs, and credits from 0.40.0. --json separates package evidence, shared sources, coverage, and diagnostics; combine it with --verbose for original source detail. Source fix lists do not establish a safe upgrade. Withdrawn and malicious-package markers are kept. See CLI commands for all flags.
pkg_deps lists a package’s direct runtime dependencies with resolved versions. Use the lifecycle parameter to include non-runtime groups (development, peer, optional, build), or pass lifecycle: "all" to see every available group. Pass max_depth to add a bounded transitive dependency footprint with conflict detection and circular-dependency flags.Pass include_issues: true (CLI --issues) to compute deprecated, outdated, duplicate, and conflict analysis across the resolved dependency graph, including actionable conflict constraints and importer provenance.CLI usage
Parameters
string
required
Package target in registry:name[@version] form, for example npm:express@5.2.1. Omit the version to inspect the latest release. Scoped names are supported. Go module versions are accepted with or without the leading v (1.24.0 or v1.24.0); other registries reject tag-style v-prefixed inputs (e.g., v4.18.0) except Swift — pass the canonical version number (4.18.0). Dependency data is available on all 13 registries: npm, PyPI, Hex, Crates, NuGet, Maven, Zig, vcpkg, Packagist, RubyGems, Go, Swift, and Pub.
string
Dependency group breadth. Omit for runtime-only. Use runtime for explicit runtime-only, a concrete non-runtime lifecycle (development, build, peer, optional) to add matching groups, or all for every available group. Accepts a single value, a comma-separated string, or an array. all cannot be combined with other values.
boolean
When true, computes deprecated, outdated, duplicate, and conflict analysis across the resolved dependency graph. Without max_depth, the analysis traverses the full graph; set max_depth to bound analysis cost and scope. Defaults to false. Use format: "json" (CLI --json) for complete issue rows, or --verbose in the CLI for complete issue details in text. In the CLI, use --issues.
boolean
When true, each entry in transitive.packages[] also carries an importers array showing every upstream package that pulls it in. If max_depth is omitted, this also requests the full transitive block. Off by default because enabling it roughly quadruples envelope size on heavy graphs.
number
Add a transitive block and cap traversal at this depth (1-10). Omit for direct dependencies only. In the CLI, use --depth.
Example
Returns: runtime, development, and peer dependency groups with resolved versions for each direct dependency.
pkg_changelog retrieves release notes for a package. Latest mode returns up to ten entries by default. Results preserve source order, which may interleave maintained release lines, so do not assume newest-first ordering. A @from..to range returns entries after from through to, with the starting version excluded and the ending version included. Use @from separately for the starting release’s own notes.From CLI and MCP 0.30.0, default text and JSON return parsed statements with available agent classifications, uncertainty markers, coverage, and sources. All matching statements are retrieved. Use changes to filter them, verbatim: true for complete original notes, or omit_bodies: true for just the version/date/URL timeline.From 0.38.0, changelog and upgrade-review output marks generated notes and their generation status. Generated notes are derived from commits; distinguish them from the project’s published release notes when citing changes.Since githits and @githits/mcp 0.21.0, pkg_changelog is package-only: the retired registry, package_name, repo_url, git_ref, from_version, and to_version inputs are replaced by a single required target, and the CLI drops --repo-url and --git-ref. Standalone repository targets are rejected. Look them up by their published package instead.CLI usage
Parameters
string
required
Package target in one of three shapes: registry:name for latest mode, registry:name@version for one selected release, or registry:name@from..to for releases after from through to. Open bounds @from.. and @..to are also accepted. Scoped names are supported. Go module versions are accepted with or without the leading v; other registries reject tag-style v-prefixed inputs except Swift. Package targets only — repository and site: targets are rejected.
number
Maximum number of entries to return (1–50, default 10). Applies only to latest mode and upper-cap @..to targets. Rejected with an exact @version, a @from..to range, or a lower-open @from.. target. Ranges with a starting version have no count cap.
boolean
When true, returns only the version/date/URL timeline and skips parsing and classification. Cannot be combined with verbatim: true or verbose: true. In the CLI, use --no-body.
string
default:"all"
Filter statements: actionable includes statements classified as requiring action, including uncertain classifications; important also includes “should know” statements; all includes every parsed statement, including no-impact and unassessed statements. Coverage still includes every selected release. Ignored in original-note and timeline views. In the CLI, use --changes.
boolean
Return complete original notes instead of parsed statements, including original bodies in JSON. Skips classification. Cannot be combined with omit_bodies: true. In the CLI, use --verbatim.
boolean
Deprecated alias for verbatim: true, in text and JSON. Overrides body_lines; cannot be combined with omit_bodies: true.
number
Deprecated text-only original-note preview request and line cap (1–50). Omit for the default statement view. Ignored with JSON, omit_bodies: true, verbatim: true, or verbose: true.
Example
Returns: up to three releases in source order with their parsed statements, available classifications, and sources. An exact version selects one release or returns VERSION_NOT_FOUND; a release without notes succeeds with hasChangelog: false. Empty latest or range selections also succeed.For scripts that need the original Markdown bodies, use verbatim: true, format: "json" or CLI --verbatim --json.
pkg_upgrade_review compares the version you use today with a target version. It checks direct vulnerability changes, changelog entries in the version range, target deprecation metadata, peer dependency changes, dependency changes, and optional transitive dependency checks.From 0.31.0, direct security summaries also retain unknown vulnerability counts and assessment status. Follow the returned pkg_vulns action to inspect advisories that could not be evaluated.Use it when your agent needs upgrade facts instead of guessing from semver. The tool reports changes; it does not decide whether an upgrade is safe.CLI usage
Use .. as the range delimiter for the positional <registry>:<name>@<current>..<target> form and for repeatable --package entries. The legacy -> delimiter is rejected with guidance to switch to ... A positional range already contains its target, so combining it with --to or --package is rejected.Parameters
string
Package registry for single-package mode. Supported registries: npm, pypi, hex, crates, nuget, maven, zig, vcpkg, packagist, rubygems, go, swift, and pub.
string
Package name for single-package mode. Scoped names are supported.
string
The version you currently use. Go module versions are accepted with or without the leading v. Tag-style inputs with a leading v are rejected for other registries except Swift.
string
The version you want to review. Go module versions are accepted with or without the leading v. Tag-style inputs with a leading v are rejected for other registries except Swift.
array
Batch mode. Each entry includes registry, package_name, current_version, and target_version. Mutually exclusive with the single-package fields. A batch accepts at most 30 packages after blank entries are removed; larger batches are rejected before any backend call.
boolean
When true, skips current-vs-target transitive vulnerability summary diffs. Defaults to false, so transitive security checks is included unless explicitly skipped. In the CLI, use --no-transitive-security.
boolean
When true, diffs current vs target transitive deprecated, outdated, duplicate, and conflict summaries. Defaults to false.
string
Minimum direct-advisory severity: low, medium, high, or critical.
string
Filter detailed changelog statements to actionable, important (actionable plus “should know”), or all. Omit for the default focused view: actionable, “should know”, and too-long-to-classify statements. focused is not an accepted explicit value. Uncertain classifications remain in their selected tier. Batch triage and coverage still describe the whole version range. In the CLI, use --changes.
boolean
Text output only. Shows full per-package reports in batch mode, expands classified statement quotes, and includes dependency change examples, including transitive version changes.
Example
Returns: a current-vs-target comparison with direct vulnerability changes, agent-classified release-note statements grouped by version, lexical keyword matches, target deprecation status, peer dependency changes, and transitive security summaries.Classified statement evidenceText output includes a Changes (classified by agent) section. An agent classifies quoted release-note statements, and the section groups them by version. Changelog or release notes links appear beside each version.
  • Action annotations such as [!] mark statements that may need a code, configuration, or migration change.
  • Should-know annotations mark statements worth knowing that are less likely to need action.
  • (uncertain) marks statements the classifier could not tier with confidence.
From 0.30.0, the detailed report includes all matching statements in release/source order. Its default focused view includes actionable, “should know”, and too-long-to-classify statements. Pass changes: "all" to also include no-impact and unassessed statements. The section reports coverage: how many versions were classified, not assessed, without notes, or unparseable. Missing or unparseable notes are not evidence of no risk. Lexical keyword matches stay in a separate list. Use verbose to expand the quotes.Batch output ranks packages by confident action count and summarizes each package’s counts, for example 13 act (+28 uncertain) | 12 know (+10 uncertain). These totals cover the whole version range even when changes filters the detailed statements.From 0.30.0, JSON uses changelog.statements instead of changelog.riskItems; riskCoverage.itemsOmitted is removed. Statement data includes complete text, source links and context, with classification and model provenance when available. Coverage retains whole-range classification totals, including itemsMustActConfident, itemsMustActAmbiguous, itemsShouldKnowConfident, itemsShouldKnowAmbiguous, and itemsUnclassified.
Migration guidesFrom CLI and MCP 0.37.0, upgrade reviews link to available migration guides for the version range. Guide links appear in detailed reports and compact batch rows. JSON keeps each guide’s URL and optional label in reviews[].migrationGuides. Your agent can open a guide when it needs migration instructions.The review includes links, not guide contents. An empty or missing migrationGuides list does not mean that no guide exists. Hosted MCP availability depends on adoption and deployment of the released package.
Classifications describe what release notes say. They are not a package verdict or a safety rating. Your agent still decides whether each statement applies to your codebase and verifies the upgrade locally.
A version number alone, including a patch update, does not establish compatibility. Use pkg_upgrade_review to collect facts, then make the final risk call in your review.

MCP tool reference