Scheduled Daily CVE Scan

Open Beginner friendly
#37 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github-actions, yaml
Domain
ci-cd, security

Research direction

Read the canonical .github/workflows/ci_scheduled.yml examples and the org-infra .github/workflows/reusable_scheduled.yml workflow. Add .github/workflows/ci_scheduled.yml with a daily cron schedule that calls the reusable workflow; done means scan results are uploaded to the GitHub Security tab.

Written by the indexing model from the issue text.

Description

enhancement

Summary

Add a daily scheduled CI job to scan for newly-disclosed CVEs in
already-merged dependencies.

Context

CI security checks run on push and PRs, but a vulnerability disclosed
after a dependency was merged goes undetected until the next PR.
The canonical reference (unbound-force/unbound-force/.github/workflows/ ci_scheduled.yml) runs OSV-Scanner and OpenSSF Scorecards daily
against the default branch to catch these.

This is a one-liner workflow — it calls a single org-infra reusable.

Acceptance Criteria

  • Add .github/workflows/ci_scheduled.yml with a cron schedule
    (e.g., 0 0 * * *)
  • Calls complytime/org-infra/.github/workflows/reusable_scheduled.yml
  • Results uploaded to GitHub Security tab

References

  • Canonical: unbound-force/unbound-force/.github/workflows/ci_scheduled.yml
  • Canonical: complytime/complyctl/.github/workflows/ci_scheduled.yml
  • Org-infra reusable: complytime/org-infra/.github/workflows/reusable_scheduled.yml
Dominant language
Go
Stars
0
Forks
9
Avg merge
1d 14h
Merged PRs (30d)
18

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 unbound-force/replicator

All issues in unbound-force/replicator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.