Skip to content

[Enhancement] Add advisory DB freshness metadata and stale warnings#84

Merged
sonukapoor merged 1 commit intomainfrom
feature/issue-79-advisory-db-freshness
Apr 4, 2026
Merged

[Enhancement] Add advisory DB freshness metadata and stale warnings#84
sonukapoor merged 1 commit intomainfrom
feature/issue-79-advisory-db-freshness

Conversation

@sonukapoor
Copy link
Copy Markdown
Collaborator

Summary:
Adds advisory DB freshness metadata and stale-data warnings so offline users can tell when their local advisory database may need to be refreshed.

Closes #79.

What changed:

  • added local advisory DB metadata storage for last sync time and source URL
  • updated advisory sync to persist freshness metadata into the SQLite DB
  • added offline CLI output for advisory DB freshness
  • added warnings when the local advisory DB is stale or missing a sync timestamp
  • added tests for metadata persistence and freshness-related CLI behavior

Notes:
This is a practical first step toward TTL-style freshness handling.

It adds built-in freshness visibility and a default stale-data signal without introducing extra configuration complexity yet.

Verification:

  • npm test
  • npm run build
  • manual end-to-end test of sync, offline scan, metadata inspection, and stale warning behavior

@sonukapoor sonukapoor merged commit 7f698db into main Apr 4, 2026
4 checks passed
@sonukapoor sonukapoor deleted the feature/issue-79-advisory-db-freshness branch April 24, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Enhancement] Add advisory DB freshness metadata and TTL-style warnings

1 participant