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

List Perl as an environment

Open
#3,536 11 comments 73 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
perl
Domain
security

Research direction

Start with the improvement form's required ecosystem field and the list of available ecosystem values; the issue mentions no files or tests. Determine how the form validates missing ecosystems and represents ecosystem metadata, then confirm the chosen behavior supports Perl-related improvements and incomplete advisory details.

Written by the indexing model from the issue text.

Description

I'd like to improve several reports related to the Perl language and ecosystem, I cannot submit the form because the improvement form has the ecosystem as a required field, and there is not entry for "Other" or some such.

I suggest some combination of these:

  • Do not require an environment value to improve a report. The allows someone to improve a report even without a listed ecosystem.
  • Use an "Unknown" or "Other" value for the ecosystem, which could either be a virtual ecosystem or simply uses no value (the current state) but still allows the form field to be required but have a null value.
  • Add Perl as an ecosystem. There are plenty of people who would help categorize the backlog of over 200,000 uncategorized reports.
  • Even without a "Perl" ecosystem, I'd still like to improve the values in the ecosystem section of the improvement form to note the versions affected, package name, and so on. In general, any improvement, even if incomplete, is valuable.
Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 15h
Merged PRs (30d)
46

Contributor guide

Open the contributing guide

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 github/advisory-database

All issues in github/advisory-database

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.