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.

Sign up for GitHub

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

Jump to bottom

Fork #208

Open
mcandre opened this issue Sep 30, 2019 · 1 comment
Open

Fork #208

mcandre opened this issue Sep 30, 2019 · 1 comment

Comments

@mcandre
Copy link

mcandre commented Sep 30, 2019

Given this repository has not been updated in quite some time, and has open security vulnerabilities, I propose that we follow an Apache-compatible license and publish an updated fork to npm as a separate package.
@mcandre
Copy link
Author

mcandre commented Oct 7, 2019

After waiting for a week for a response to the security reports, I went ahead and started up a "jsfmt2" project.

https://github.com/mcandre/jsfmt2

It's not 100% npm audit passing, but it's a lot better than it was. The few remaining CVE's are rated "Low", in a dependency that hasn't seen much maintenance. (Shall we fork this as well?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcandre