Store allowlist of third-party plugins in a JSON file

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Locate the current approved-plugin allowlist in the repository codebase and read how it is consumed. Move the list into a JSON file containing each npm package name, description, and repository, then verify the scanner still discovers the existing plugin from that file.

Written by the indexing model from the issue text.

Description

From @edsummersnc:

Consider refactoring the list of approved plugins into a JSON file or similar file type. Include npm package name, description, and repo. This will allow users of the scanner to find third-party plugins, perform their own security review, file issues on those plugins, contribute fixes, fork/extend, etc.

The allowlist is currently maintained in the repo's codebase, as it contains only a single entry.

Dominant language
TypeScript
Stars
374
Forks
42
Avg merge
1d 9h
Merged PRs (30d)
10

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/accessibility-scanner

All issues in github/accessibility-scanner

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.