Is v1 desupported?

[LunaticMuch]

It might be I did not find it, but is the v1 desupported? Many libraries still use v1 and I've found a security issue with trim

 @docusaurus/[email protected]
  └─┬ @docusaurus/[email protected]
    └─┬ @mdx-js/[email protected]
      └─┬ [email protected]
        └── [email protected]

An update to [email protected] should quickly solve the trouble.

[ChristianMurphy]

Please see any of the many times this question has been asked https://github.com/mdx-js/mdx/issues?q=is%3Aissue+trim+is%3Aclosed+vulnerable and discussed https://github.com/mdx-js/mdx/discussions?discussions_q=trim+security

To reiterate:

1. This is not an exploit, it is a potential slow down. remark-parse 9+, react-markdown 6+, and mdx 2 address this, and provide other performance improvements.
   https://overreacted.io/npm-audit-broken-by-design provides some additional insights into why npm audit and snyk, while useful, can also be broken for packages like react and mdx, flagging non-issues.
2. MDX version 1 cannot be patched (less strict version dependecy for "remark-parse" #1548 (comment))
3. MDX version 2 no longer uses trim as a dependency