Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moo-server 1.3.0 #10065

Merged
merged 3 commits into from
Apr 30, 2021
Merged

moo-server 1.3.0 #10065

merged 3 commits into from
Apr 30, 2021

Conversation

clearlydefinedbot
Copy link
Contributor

Type: Missing

Summary:
moo-server 1.3.0

Details:
Add BSD-3-Clause License

Resolution:
License Url:
https://github.com/no-context/moo/blob/master/LICENSE

Description:

Pull request generated by Microsoft tooling.

Affected definitions:

@clearlydefinedbot
Copy link
Contributor Author

You can review the change introduced to the full definition at ClearlyDefined.

@LandOfBliss LandOfBliss self-assigned this Mar 12, 2021
@LandOfBliss
Copy link

  1. Looked in the "Files" section in the ClearlyDefined definition. No license file found. moo-server 1.3.0 was released on December 17, 2011 to NPMJS
  2. Looked in the package.json in the "Files" section on the ClearlyDefined definition. No license file or reference.
  3. Looked for source on NPMJS: https://www.npmjs.com/package/moo-server/v/1.3.0 License is identified as NONE. No link to GitHub repository. No package.json file.
  4. The Resolution license URL submitted in the Pull Request links to: https://github.com/no-context/moo/blob/master/LICENSE The package.json file on GitHub indicates BSD-3-Clause. However, the license file (https://github.com/no-context/moo/blob/c75678b85010e0c75d6b85b4f913bdfdad6a6a89/LICENSE) was first committed to the project on June 18, 2017 after the release of moo-server 1.3.0 to NPMJS. "moos-server 1.3.0" appears to be different from the GitHub component "no-context/moo"
    Conclusion: The declared license is NONE

@ariel11
Copy link
Contributor

ariel11 commented Mar 15, 2021

@LandOfBliss - I agree with NONE.

@ariel11 ariel11 added the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Mar 15, 2021
@github-actions github-actions bot removed the merge conflict GitHub Action bot will auto add/remove this label when there's a conflict. label Mar 15, 2021
@github-actions
Copy link

Conflicts have been resolved.

@ariel11 ariel11 added the issue There is a tooling or process based issue or question. label Mar 15, 2021
@nellshamrell nellshamrell reopened this Apr 26, 2021
@capfei capfei removed the issue There is a tooling or process based issue or question. label Apr 30, 2021
@capfei capfei merged commit 986966a into master Apr 30, 2021
@capfei capfei deleted the clearlydefinedbot_210311_213302.510 branch April 30, 2021 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants