Validate package metadata
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 105
- Forks
- 34
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Validate package metadata against spec errors, do not include superfluous fields and do not allow type errors.
We can also add separate, optional functions to validate package metadata for warnings, we can pass it a list of policies that can be used, like (hexpm/public/private). We could handle the tarball size validation the same way to not be locked into hexpm specifics.
NOTE: Do not include maintainers in the package metadata.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the existing package-metadata handling and comparing it with the relevant Hex specification; completion should cover metadata errors, type errors, superfluous fields, and the explicit exclusion of maintainers, while the optional warning-policy and tarball-size scope needs clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100