Missing license information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 27
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
vbare is missing a license field in package.json and there's no LICENSE file in the published npm package. We use rivetkit and vbare comes in as a transitive dependency. In our automated license checks vbare is then being flagged (as having unknown license). In your blog post, vbare has been described as being open-source and has MIT mentioned in the README.
However, is it please possible to clarify and add the correct LICENSE file to the repo/package info?
Thank you,
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
Start by checking package.json, the repository README, and the published npm package for the current license declarations and included files. Confirm the intended license with the existing README and blog reference, then ensure the repository and published package expose matching license information and verify the package contents.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100