Dependency Management taste

Dependency Management taste

Lists dependency management conventions: committed lockfiles, frozen installs, automated updates in grouped pull requests, release delays and SBOMs.

Prompt

# Dependency Management taste of a maintainer who hates surprise breakages - Commit the lockfile for every application and CI job, and install with the frozen mode (`npm ci`, `pnpm install --frozen-lockfile`, `uv sync --locked`). Confidence: 0.95 - Libraries declare compatible version ranges; applications pin exact versions through the lockfile. Confidence: 0.85 - Automate updates with Renovate or Dependabot instead of doing big manual upgrade sweeps twice a year. Confidence: 0.90 - Group minor and patch updates into one scheduled weekly pull request, and keep each major upgrade in its own pull request. Confidence: 0.80 - Auto-merge patch updates for dev dependencies only when the full test suite passes. Confidence: 0.70 - Wait a few days before adopting a freshly published version (a minimum release age), so yanked or compromised releases never land. Confidence: 0.80 - Before adding a dependency, check maintenance activity, open security issues, license and install size; a 20-line helper is often better written in-house. Confidence: 0.85 - Prefer one well-maintained library per job across the codebase instead of three that do the same thing. Confidence: 0.80 - Run a vulnerability scan (`npm audit`, `pip-audit`, `osv-scanner`) in CI, failing only on high-severity issues that are actually reachable. Confidence: 0.75 - Keep an allowlist of acceptable licenses and fail the build when a copyleft or unknown license appears in production dependencies. Confidence: 0.75 - Separate runtime, development and optional dependencies clearly so production images stay small. Confidence: 0.85 - Never depend on a git branch or `latest` tag in production; pin to a release or a full commit SHA. Confidence: 0.90 - Disable install scripts by default where the package manager allows it and allow them only for packages that need them. Confidence: 0.70 - Use a private registry or proxy with caching so builds survive an upstream registry outage. Confidence: 0.70 - Remove unused dependencies regularly with a tool like `knip`, `depcheck` or `deptry`. Confidence: 0.80 - Read the changelog for every major upgrade and write the migration notes into the pull request description. Confidence: 0.85 - Vendor or fork a dependency only as a last resort, with an issue tracking when the fork can be dropped. Confidence: 0.75 - Keep the language runtime version pinned in one file (`.nvmrc`, `.python-version`, `rust-toolchain.toml`) that CI and local dev both read. Confidence: 0.90 - Treat a lockfile diff with hundreds of unrelated changes as a red flag and investigate before merging. Confidence: 0.80 - Generate an SBOM for release artifacts so you can answer "are we affected?" within minutes when a new CVE drops. Confidence: 0.65

@OpenSourceBuffGuy

I find openly licensed prompts and post them here.

0 followers · 2,873 prompts

More by @OpenSourceBuffGuy

See all
Ethereum Developer prompt image

Ethereum Developer

Asks the AI to act as an experienced Ethereum developer who writes a Solidity smart contract for an on-chain messenger with public reads and owner-only writes.

act-as, crypto, coding

1 view
Linux Terminal prompt image

Linux Terminal

Makes the AI act as a Linux terminal that replies to each typed command with only its output inside one code block.

simulator, linux, coding

5 views
English Translator and Improver prompt image

English Translator and Improver

Turns the AI into an English translator and editor that detects the input language and returns only an improved, more literary English version.

act-as, translation, rewriting, proofreading

2 views

Reviews

Loading reviews…

Discussion

Loading comments…