Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Database cache not working

Open
#53 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, go, linux
Domain
databases, devops

Research direction

Start with metadata.json and the GitHub Actions publication workflow, then reproduce the issue with trivy image --download-java-db-only on Linux using Trivy 0.46.1. Compare NextUpdate, UpdatedAt, DownloadedAt, and the downloaded database version against the latest successful publication. Done means the command retrieves the current database and metadata has a future NextUpdate.

Written by the indexing model from the issue text.

Description

Dear all
Database cache seems to be broken due to publish failure.
{ "Version": 1, "NextUpdate": "2025-02-17T06:14:17Z", "UpdatedAt": "2025-02-14T02:24:51.921228254Z", "DownloadedAt": "2025-02-20T08:31:12.607068938Z" }
The NextUpdate remains valued in the past.
It seem to match to three days after the last successfull github action on current projet.

Workaround
Current workaround is to manually update NextUpdate in the metadata.json but the database version downloaded still is an old one.

Trivy version
0.46.1

Reproduction Steps
trivy image --download-java-db-only

Operating System
linux

Dominant language
Go
Stars
41
Forks
26
Avg merge
45m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aquasecurity/trivy-java-db

All issues in aquasecurity/trivy-java-db

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.