Topic

#dependabot

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#dependabot

Loot

More from this topic

Explore all loot

Use Dependabot's default cooldown before merging fresh package releases

#github #dependabot+3

GitHub now waits three days before opening Dependabot version-update pull requests, reducing exposure to compromised or broken package releases. GitHub has changed Dependabot version updates so new package releases must sit in the registry for at least three days before Dependabot opens a version-update pull request. Security updates still open immediately. Use this as a low-friction supply-chain safety check. The default gives maintainers and the wider ecosystem time to flag compromised, yanked, or broken releases before they land in routine dependency-update PRs. What to do Leave the new default in place for most repositories. Keep security updates immediate; the cooldown applies to version updates, not urgent security fixes. Override the window in .github/dependabot.yml only when your release process has a clear reason. Watch high-risk ecosystems or critical services for packages that should use a longer cooldown. Best fit Repository type Suggested move Caveat --- --- --- Standard app repos Keep the three-day default Review lockfile-only bumps before merge Security-sensitive services Consider a longer cooldown for non-security updates Do not delay patched security advisories Fast-moving libraries Tune per ecosystem in dependabot.yml Document why the shorter window is acceptable

Free

Review open

@ZachasADMIN

Open loot

Use GitHub innersource advisories to push private dependency fixes inside an enterprise

#github #security+3

GitHub Advanced Security enterprise customers can now publish private innersource security advisories that trigger internal Dependabot alerts and fix PRs. GitHub innersource advisories are now generally available for enterprise security teams that need private vulnerability distribution inside one company. Use them when an internal package, shared service, or private fork has a flaw that should trigger Dependabot alerts and update pull requests without publishing the advisory to the public GitHub Advisory Database. The workflow is narrow and useful: create or withdraw advisories through the REST API, keep visibility scoped to the enterprise, and let Dependabot notify repositories that depend on the affected component. It is a fit for internal platforms, monorepos split into reusable packages, and regulated teams that need coordinated remediation before public disclosure. Check What to verify --- --- License Requires active GitHub Code Security or GitHub Advanced Security. Scope Advisories apply to the entire enterprise, not selected org groups. Limit Each enterprise can have up to 2,000 active innersource advisories. Automation Dependabot can create alerts and version update PRs for affected repos. Disclosure Advisory data stays private to the enterprise unless separately published. Treat this as a private remediation lane, not a replacement for public CVEs or external disclosure when customers or open-source users are affected.

Free

Review open

@ZachasADMIN

Open loot

Blog

#dependabot

More from this topic

Use Dependabot's default cooldown before merging fresh package releases

Use GitHub innersource advisories to push private dependency fixes inside an enterprise

Related reads

Delay Dependabot Version PRs Before Fresh Packages Hit Your Build

Use GitHub Innersource Advisories before internal packages hide security fixes

Audit Dependabot alert exports before GitHub moves old closed alerts out of the API

Fix Dependabot npm registry scope before private package updates drift