CVE tracking

Open
#73 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
github-actions, typescript
Domain
security

Research direction

The issue names no files, entry points, tests, or acceptance criteria. Start by reviewing the repository structure and existing GitHub Actions to determine where CVE tracking would belong; the work is done only when a defined tracking workflow and its expected behavior are agreed and tested.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
TypeScript
Stars
6
Forks
9
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 elastic/github-actions

All issues in elastic/github-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.