package-usage
Track which stacks across a Pulumi organization use a specific package and at what versions. Use for cross-stack audits, identifying outdated or unmaintained…
npx skills add https://github.com/pulumi/agent-skills --skill package-usageAPI Reference
Query the Pulumi Cloud API with the pulumi api CLI subcommand. It authenticates with your existing Pulumi credentials and returns JSON.
Get the latest version of a package
pulumi api /api/registry/packages -F name={package_name} -F orgLogin={orgName}
Include orgLogin with the user's organization name. Omit -F name=... to list all packages visible to the organization (useful when the user has not named a specific package). The response contains a packages array. Each entry has a version field (the latest version), plus name, publisher, source, and packageStatus.
Get stack usage for a package
pulumi api /api/orgs/{orgName}/packages/usage -F packageName={package_name}
Replace {orgName} with the org name from context, PULUMI_ORG, or ask the user. packageName is required; query one package at a time.
Response fields:
packageName: The queried packagestacks: Array of{stackName, projectName, version, lastUpdate}totalStacks: Total count
Workflow: Find outdated stacks
Use when the user wants to know which stacks are using an outdated version of a package.
- Get the latest version of the package
- Get stack usage for the package
- Compare each stack's
versionagainst the latest to identify outdated stacks - Present results using the output format below
Output Format
Present results as a markdown table followed by a summary line:
| Project | Stack | Current Version | Latest Version | Status |
|---------|-------|-----------------|----------------|--------|
| my-app | dev | 6.40.0 | 6.52.0 | Outdated |
| my-app | prod | 6.52.0 | 6.52.0 | Up-to-date |
2 of 2 stacks checked. 1 outdated.
Out of scope: upgrading a specific stack
This skill identifies outdated stacks. It does not perform the upgrade itself. For actually bumping a package version in a project — editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml, running pulumi preview, and reconciling the diff — hand off to the provider-upgrade skill.