[Question] What licenses cover version-fox/version-vault, version-fox/vfox-plugins and version-fox/homebrew-tap?

Open
#772 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active

Research direction

The issue is a licensing question, not a code change: read package.json in version-fox/version-vault, which declares "license": "MIT" without the license text, and the README of version-fox/vfox-plugins, which states nothing. Only a maintainer can decide the license, so start by asking them to confirm the terms for both repositories. Done means a LICENSE file with the full text is added at each repository root and the README or package.json agrees with it.

Written by the indexing model from the issue text.

Description

help wanted question

Version
N/A. This concerns the repositories version-fox/version-vault, version-fox/vfox-plugins and version-fox/homebrew-tap, not a vfox release.

OS
N/A

Question Description
None of these three repositories has a license that GitHub recognizes, and none has a license file at its root.

  • version-fox/version-vault: there is no LICENSE file, and GitHub reports no license. package.json declares "license": "MIT", but the repository does not contain the MIT license text.
  • version-fox/vfox-plugins: there is no license file, and the README does not state a license.
  • version-fox/homebrew-tap: there is no license file, GitHub reports no license, and there is no README. It contains two vfox formula files, vfox.rb at the root and Formula/vfox.rb, both generated by GoReleaser. Both declare license "Apache-2.0", which is the license of vfox, the software they install. That does not say which terms apply to the tap's own files.

What license applies to each repository? If it is MIT or another OSI-approved license, please add the full license text as a LICENSE file. If it is a license that is not OSI-approved (for example, source-available or proprietary), please say so and include that license's text. Anyone who packages or redistributes these repositories needs to know the terms.

Dominant language
Go
Stars
4k
Forks
177
Avg merge
1d 20h
Merged PRs (30d)
31

Getting set up

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 version-fox/vfox

All issues in version-fox/vfox

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.