I'm working on a project with some very tight security protocols. There is a vulnerability, that I believe is fixed on master; however, a new version has not been released. The editor I use (simplemde) uses the latest version of Marked by default; so, as soon as the release is made, I can get this approved in my environment.
Please.
I second that idea, as David DM now marks marked as unsecure (e.g. see https://david-dm.org/fboes/blogophon). For some unlucky folks this means that on _their_ project page their project is marked as unsecure.
The person that owns the project will not respond / push a new version and us maintainers on github can't push to NPM.
I would consider this project dead. I would be happy to consider a fork or maybe people should look into something like markdown-it.
@matt- I was afraid that would be the case. Do you know if others feel the same? (I mean with 300+ Issues and 150+ PRs can't imagine it not being the case.)
(I really do hope @chjj is all right...recent activity seems a little light in comparison.)
Everyone is welcome to head over to 8fold/marked. I will be happy to add collaborators to the repo and NPM for the project (don't know the details of how and process for releases yet, but we'll get it sorted).
This seems to be one of the more popular Markdown libraries going and I don't think the broader community is ready to abandon it wholesale. If there's a way to get the owner to transfer ownership, 8fold is willing to take that on as well to maintain the "marked" package name and whatnot.
@colinalford-gsa
As for the time being I switched to https://www.npmjs.com/package/8fold-marked, but will return to the original as soon as it is patched.
We just did release 0.3.8 with a performance enhancement.
https://github.com/8fold/marked/pull/1
There are two more PRs in the queue:
https://github.com/8fold/marked/pulls
I don't know demand for those; so, not sure the urgency. Looks like they were pulled over from PRs submitted here that the submitters were waiting on.
Also we have another collaborator for the library with write access; so, I believe they should be able to accept PRs. Invited @matt- as well. So, far I'm not too concerned about the bottleneck at NPM yet. Trying to build a core team...temporary as it may or may not become.
Reached out to @chjj to see about transferring the project to 8fold. We'll see how that goes.
As I have been granted publishing rights to NPM and collaborator rights on the repo, I will close this issue for now. See #956 and #951.