Scheduled Daily CVE Scan
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
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
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.ymlwith 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from unbound-force/replicator
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#95 ·
Maintainers usually reply within 1 day
-
bug github_actions
Difficulty 2/5 Under an hour Newbie friendliness 80/100
unbound-force/replicator#89 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#85 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unbound-force/replicator#77 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
unbound-force/replicator#63 ·
Maintainers usually reply within 1 day
All issues in unbound-force/replicator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day