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

Consider replacing showdown #1083

Closed
vsgoulart opened this issue Mar 5, 2024 · 3 comments
Closed

Consider replacing showdown #1083

vsgoulart opened this issue Mar 5, 2024 · 3 comments
Assignees

Comments

@vsgoulart
Copy link
Contributor

What should we do?

showdown has a possible CVE we need to investigate and possibly replace it
A possible alternative is marked

Why should we do it?

To have no vulnerabilities

@vsgoulart vsgoulart self-assigned this Mar 5, 2024
@Skaiir
Copy link
Contributor

Skaiir commented Mar 6, 2024

I feel like we actually replaced marked by showdown. Or maybe it was another framework, but anyways does marked actually support GFM?

@vsgoulart
Copy link
Contributor Author

I feel like we actually replaced marked by showdown. Or maybe it was another framework, but anyways does marked actually support GFM?

@Skaiir We replaced snarkdown with showdown

@nikku nikku added the backlog Queued in backlog label Mar 7, 2024 — with bpmn-io-tasks
@bpmn-io-tasks bpmn-io-tasks bot added needs review Review pending in progress Currently worked on and removed backlog Queued in backlog needs review Review pending in progress Currently worked on labels Mar 7, 2024
@bpmn-io-tasks bpmn-io-tasks bot removed the needs review Review pending label Mar 14, 2024
@nikku
Copy link
Member

nikku commented Mar 26, 2024

The replacment train keeps on rolling 🙂

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

No branches or pull requests

3 participants