Is Package Usage safe and trustworthy?

tashan scores Package Usage on public evidence — it is currently abandoned. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Package Usage?

Don't. This capability has been discontinued by its author or publisher and is not scored or recommended. If you are already running it, `npx tashan-cli doctor` will flag it and name what to move to.

‹ The Index

Package Usage

skill

Track which stacks across a Pulumi organization use a specific package and at what versions. Use for cross-stack audits, identifying outdated or unmaintained package versions across many stacks, finding affected stacks before publishing breaking changes to a component package, or planning coordinated upgrade rollouts. Do NOT use for upgrading a cloud provider package (pulumi-aws, pulumi-azure-native, pulumi-gcp, pulumi-kubernetes, etc.) in a single project — use skill provider-upgrade instead. Do NOT use for general infrastructure creation, resource provisioning, or how-to questions about a package.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Discontinued — do not install. The author's own notice: “Track which stacks across a Pulumi organization use a specific package and at what versions. Use for cross-stack audits, identifying outdated or unmaintained package versions across many stacks, findi” It stays listed so anyone already running it can find this page, and so npx tashan-cli doctor can warn about it. It is not scored and does not appear in any ranking.

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

Adoption: 1 repos
Health: abandoned

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, says when not to and shows worked examples.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:pulumi/package-usage

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-20 · scorer s5 · how · something wrong here?