
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
delete-cache-action
Advanced tools
GitHub action for deleting cache with a specified key.
Delete the cache with a specific key:
- uses: prantlf/delete-cache-action@v2
with:
key: newchanges-linux-x64.zip-${{ github.sha }}
The following parameters can be specified using the with object:
Type: String
The cache key to delete. Mandatory.
Type: String
Default: ${{ github.token }}
Authorization token to access the cache in the target repository. Either a GitHub personal access token or the GitHub workflow token. If not provided, the environment variable GITHUB_TOKEN will be used as a fallback. And if even that is not set, the GitHub workflow token from the action-execution context will be used as default.
Copyright (C) 2023 Ferdinand Prantl
Licensed under the MIT License.
FAQs
GitHub action for deleting cache with a specified key.
The npm package delete-cache-action receives a total of 2 weekly downloads. As such, delete-cache-action popularity was classified as not popular.
We found that delete-cache-action demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.