With this many issues and PRs, I wonder if the project still lives when its 7 months since last update?
vongohren
All 17 comments
+1
lferreirawork
on 22 Feb 2016
The project not being worked on is not an "issue" with the code, and posting observations like these to the issue tracker is just cluttering it up. If you want to ask the maintainer about this project's future, please just contact him directly.
webbedspace
on 23 Feb 2016
@webbedspace i feel that it's important to raise the issue to make other who probably are thinking the same, aware of whats happening. I have many times seeked the issuetracker to see if this question have been asked, and if a response have been made. Sometimes this issue can spark the contribution spirit in someone who will fork the project and keep it maintained somewhere else. Its all about sheeding light on an issue with the repository.
vongohren
on 23 Feb 2016
:+1:
anaran
on 23 Feb 2016
@Snorlock Good point. And since this project's last commit would be nearly 7 months ago ( and 127 PRs waiting to be merged ), it's easy to doubt that if this project is still on the track.
allenfantasy
on 24 Feb 2016
Yeah I believ it myself, but I want a comment from @chjj
vongohren
on 24 Feb 2016
+1
sn3p
on 26 Feb 2016
i'd say this project is dead..
can anyone recommend a reliable fork to switch to? If not, does anyone have a day or two free to create one and work through the pile of outstanding PRs?
75lb
on 3 Mar 2016
:+1:
Ir1d
on 3 Mar 2016
@75lb Not a fork, but https://github.com/markdown-it/markdown-it is the most active markdown plugin for js right now, it was a fork of https://github.com/jonschlinkert/remarkable.
JCMais
on 3 Mar 2016
How about https://github.com/showdownjs/showdown?
leocaseiro
on 5 Apr 2016
The Code doesn't age.
ghost
on 1 May 2016
@wifiextender it is kind of sad that now there is a code vulnerability in it and we can't get that fixed. Is there an ability to move this to another maintainer? npm rights and such @chjj
gabrielcsapo
on 15 May 2016
@chjj vscode is using this and they are moving away from it because of lack of movement on the project...
gabrielcsapo
on 20 May 2016
+1
akuma
on 13 Jun 2016
Please see https://github.com/chjj/marked/issues/756
tcurdt
on 13 Jun 2016
Closing for cleanup
vongohren
on 22 Aug 2017
Related issues
thyxsl
路
4Comments
zoe-cjf
路
3Comments
raguay
路
4Comments
chunhei2008
路
3Comments
learykara
路
3Comments
Most helpful comment
@webbedspace i feel that it's important to raise the issue to make other who probably are thinking the same, aware of whats happening. I have many times seeked the issuetracker to see if this question have been asked, and if a response have been made. Sometimes this issue can spark the contribution spirit in someone who will fork the project and keep it maintained somewhere else. Its all about sheeding light on an issue with the repository.