-
Notifications
You must be signed in to change notification settings - Fork 215
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
Is this project dead? #245
Comments
Related: #223 (comment) |
See https://github.com/RSeidelsohn/license-checker-rseidelsohn as a possible active fork. |
Looks dead to me, as well. |
Possible replacement: https://github.com/microsoft/license-checker-webpack-plugin |
@davglass is taking sabbatical from Open Source @Bosch-Eli-Black @johnthagen we just forked it and are going to extend / continue to support work on at @bluenovaio. We will need to take some time to review the issues that are open and try and get the reporter to open on our repository once we are ready. We will need to review license and other documents to adhere with our standards. |
That's great. Please take a look at https://github.com/RSeidelsohn/license-checker-rseidelsohn as they fork added some nice fixes and improvements as well. |
@zrosenbauer Cool! 🙂 I've starred your project. |
Since @RSeidelsohn's fork is still active, pinging him for awareness. Perhaps you two can collaborate. Would be great to have this project revived. ❤️ |
Yea I’ll reach out and see what we can do.
On Mon, Mar 22, 2021 at 6:24 AM johnthagen ***@***.***> wrote:
Since @RSeidelsohn <https://github.com/RSeidelsohn>'s fork is still
active, pinging him for awareness. Perhaps you two can collaborate. Would
be great to have this project revived. ❤️
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#245 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2TF7LBPPQJBRRE5FGUCUTTE4SFXANCNFSM4RU4RSJQ>
.
--
Sent from Gmail Mobile
|
Yes, this project should not die. I love my job as a FE dev, but it's a full time job and in my spare time I care for my wife and our two children, which is pretty time consuming. Also, I try to find time for my (other) hobby as well - home brewing. So I do not find too much time caring for this project. Yet it is great for giving a small contribution to the community and it helps honing my skills and it is fun as well. So that being said, I try to do my best, yet I happily accept pull requests. This project is really small and should be great for beginning contributors as well. Cheers and thanks for the pings! |
@RSeidelsohn can you shoot me an email at [email protected], I'd love to chat briefly about this project with you if you have a chance. Cheers. |
@zrosenbauer is the bluenovaio fork defunct or moved? The link doesn't appear to work for me. As someone looking to use this tool, should I be using the rseidelsohn fork or the bluenovaio fork? |
I've found @RSeidelsohn's fork to work great. He's fixed several issues with the base repo. I haven't had any issues with his fork. |
Don’t use BlueNova fork, still WIP use reidelsohn‘s!
johnthagen ***@***.***> schrieb am Mo. 16. Aug. 2021 um 12:06:
As someone looking to use this tool, should I be using the rseidelsohn
fork or the bluenovaio fork?
I've found @RSeidelsohn <https://github.com/RSeidelsohn>'s fork to work
great. He's fixed several issues with the base repo. I haven't had any
issues with his fork.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#245 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2TF7PXV3VJAFSACCCQ7TLT5FAQZANCNFSM4RU4RSJQ>
.
--
Sent from Gmail Mobile
|
This replaces the npm package license-checker by an active fork named license-checker-rseidelsohn For further details see davglass/license-checker#245 (comment)
This replaces the npm package license-checker by an active fork named license-checker-rseidelsohn For further details see davglass/license-checker#245 (comment) Additionally @neohelden/eslint-config will be allowed
@johnthagen @Bosch-Eli-Black @RSeidelsohn @brebory @zrosenbauer As the author of |
@codepunkt We use a fork of Here is an example of creating such a report: |
We have a similar use case as @johnthagen: We generate a static license report of all NPM dependencies and feed that to a an OSS license scanner tool (similar to Blackduck). We're currently using https://github.com/microsoft/license-checker-webpack-plugin, but that's repo is no longer maintained, as the owner of the repo is no longer at Microsoft. |
@johnthagen That's what I was suspecting most people would do with
@Bosch-Eli-Black Switching to I'm not trying to dismiss the awesome work the author and maintainer has done here. This repository was the starting point for our license compliance tooling aswell. I'm just trying to be realistic here - it is not a good choice if license compliance is important to you or your company to use it to generate bills of material. |
There have been no commits for 1.5 years: https://github.com/davglass/license-checker/commits/master
Perhaps the README should be updated that this project is abandoned, if it is?
The text was updated successfully, but these errors were encountered: