Skip to content

GitHub Action to fix stuck Dependabot alerts using Copilot Workspace

Notifications You must be signed in to change notification settings

engseclabs/dependabot-wolf

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Dependabot Wolf 🐺

When Dependabot gets stuck, Wolf shows up.

image

The Problem

Dependabot says "cannot update to a non-vulnerable version" when dependency graphs are too complex. Alert sits there. Nobody fixes it.

What Wolf Does

  1. Finds stuck Dependabot alerts (no PR exists)
  2. Creates an issue with vulnerability details
  3. Assigns it to Copilot

Copilot attempts the fix and creates a PR. Might work, might not - but at least it tries.

Setup

1. Create a PAT

  1. SettingsDeveloper settingsPersonal access tokensFine-grained tokens
  2. Generate new token
  3. Repository access: Select your repo
  4. Permissions:
    • Actions: Read and write
    • Contents: Read and write
    • Dependabot alerts: Read-only
    • Issues: Read and write
    • Pull requests: Read and write
  5. Copy token

Why these permissions?

2. Add Secret

  1. SettingsSecrets and variablesActions
  2. New repository secret
  3. Name: DEPENDABOT_PAT, Value: your token

3. Add Workflow

Copy .github/workflows/dependabot-wolf.yml to your repo.

4. Enable Dependabot

SettingsCode security and analysis → Enable Dependabot alerts

Done. Runs daily at midnight, or manually via Actions tab.

Notes

  • Always review PRs before merging
  • Tested with npm and Go, should work with other package managers
  • "If I'm curt with you it's because time is a factor." - Mr. Wolf

License

MIT

About

GitHub Action to fix stuck Dependabot alerts using Copilot Workspace

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •