WordPress / WordPress/plugin-check
Custom/Private Plugins not in the Wordpress Repository
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 362
- Forks
- 126
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
PCP checks for naming collisions with plugins in the Wordpress Repository and reports if issues are found.
I would like to propose a new feature to extend this name collision check for the benefit of End Users.
This would warn an End User if the plugin they are checking is not in the Wordpress Repository. Also to provide cautionary advise that the plugin has not been subject to the more extensive testing that is normally required. Maybe with a security caution message/icon.
End Users might find this useful in cases where the website was constructed by others or in situations where security issues were a concern.
Contributor 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.
Research direction
Start by locating the existing plugin name-collision check and how it queries the WordPress Repository. Define the behavior for plugins absent from the repository, including the cautionary security message or icon, and verify that existing collision checks remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100