actions/cache

Cache dependencies and build outputs in GitHub Actions

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 12th, 2026
Created on October 16th, 2019
Open Issues & Pull Requests: 240 (+0)
GitHub issues: Enabled
Number of forks: 1,592
Total Stargazers: 5,546 (+0)
Total Subscribers: 119 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 days
Mean response time: 57.1 days
90th percentile: 200.4 days
Tracked items: 160

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 58% of tracked open issues have had no activity in three months. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 597 days
Stale 30+ days: 119
Stale 90+ days: 94

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (12)
  • bug (8)
  • documentation (7)
  • enhancement (7)
  • feature request (6)
  • invalid (5)
  • area:compression (2)
  • area:docker-cache (2)

Detailed Description

actions/cache is a GitHub Actions action that caches dependencies and build outputs to improve workflow execution time.

The action addresses the problem of slow workflow runs by storing build artifacts and dependencies between job executions, eliminating the need to rebuild or re-download them each time. It works by saving specified paths to cache storage during a workflow run and restoring them in subsequent runs when the cache key matches, reducing overall execution time for CI/CD pipelines.

Teams using GitHub Actions should adopt this tool if they have workflows that repeatedly install dependencies or build artifacts that can be reused across runs. It suits any project with package managers, compiled outputs, or other cacheable build artifacts. The README documents two companion actions available alongside the primary cache action: a restore action and a save action, allowing fine-grained control over caching behavior if needed.

The project has undergone significant backend infrastructure changes, with the cache service rewritten for improved performance and reliability. The tool has migrated to an ESM module system and updated its runtime to Node.js 24, requiring a minimum Actions Runner version of 2.327.1 for compatibility. The project maintains backward compatibility across these changes, though users on self-hosted runners must update their runner versions to ensure the action functions correctly after the service migration.