Hacker News: hanyiwang

New comment by hanyiwang in "Show HN: Agent Vault – Open-source credential proxy and vault for agents"

hanyiwang — Wed, 22 Apr 2026 16:48:17 +0000

This doesn't change the fact that you'd still be able to exfiltrate data like sure they don't get credentials but if they get the proxy auth key then they would also be able to make requests through it no?

New comment by hanyiwang in "Comparing Auth from Supabase, Firebase, Auth.js, Ory, Clerk and Others"

hanyiwang — Wed, 23 Oct 2024 16:52:17 +0000

Would also like to give a shoutout to Stytch. We've used them since day 0 to build our entire auth system, and have found the overall dev experience to be quite great

New comment by hanyiwang in "Mintlify GitHub read/write token leak"

hanyiwang — Mon, 18 Mar 2024 03:13:46 +0000

Hey Ethan! Han from Mintlify here.

It's been awhile I hope you're doing well!

The vulnerability issue that you reported, if I recall correctly, was relating to server-forwarding attacks via our API playground. We've addressed that issue around 8 months ago, and unfortunately, it was not the root of this incident.

Please correct me if I am wrong though!

New comment by hanyiwang in "Mintlify GitHub read/write token leak"

hanyiwang — Sun, 17 Mar 2024 18:27:34 +0000

This is Han, I'm one of the co-founders from Mintlify.

For the security of our customers from the publicity we were expecting from the announcement, we've decided to leave out the technical details of the breach in the blog post.

The source of this security incident was due to an uncaught error response in one of our APIs that didn't properly format the response before sending it back to the client. The response contained our internal admin tokens, which can then be used to access internal endpoints, which unveiled sensitive user information.

Our initial patch upon discovering the incident fixed the response of the vulnerable endpoint, but we have since also implemented a sweeping number of security provisions and are also in the process of completely deprecating the admin tokens and GitHub OAuth entirely to prevent an incident like this from ever happening again.

Mintlify's Journey Through YC

hanyiwang — Tue, 11 Jul 2023 06:27:28 +0000

Article URL: https://mintlify.com/blog/ycombinator

Comments URL: https://news.ycombinator.com/item?id=36677106

Points: 1

# Comments: 0

New comment by hanyiwang in "How to mitigate risk from secrets leaks"

hanyiwang — Sat, 27 May 2023 22:25:08 +0000

and that's why you use secret managers like infisical

Mintlify: Documentation That Converts Users

hanyiwang — Fri, 11 Nov 2022 05:46:00 +0000

Article URL: https://mintlify.com/

Comments URL: https://news.ycombinator.com/item?id=33557685

Points: 1

# Comments: 0

Show HN: Open-Source ReadMe Alternative

hanyiwang — Wed, 12 Oct 2022 16:05:29 +0000

Article URL: https://github.com/mintlify/mint

Comments URL: https://news.ycombinator.com/item?id=33179010

Points: 10

# Comments: 3

OS docs generator that's easier and more beautiful that Docusaurus

hanyiwang — Fri, 23 Sep 2022 02:05:23 +0000

Article URL: https://github.com/mintlify/mint

Comments URL: https://news.ycombinator.com/item?id=32947158

Points: 2

# Comments: 0

Ask HN: How important is documentation in your purchasing decision?

hanyiwang — Sat, 23 Jul 2022 01:34:32 +0000

Comments URL: https://news.ycombinator.com/item?id=32199313

Points: 1

# Comments: 0

Why do people use JSDocs, RustDoc, or others

hanyiwang — Fri, 01 Jul 2022 18:24:49 +0000

Who's using the generated results for JSDocs or equivalent in other languages? What's useful about it?

Comments URL: https://news.ycombinator.com/item?id=31950626

Points: 3

# Comments: 0

Open source AI docstring generator

hanyiwang — Fri, 01 Jul 2022 14:36:24 +0000

Article URL: https://github.com/mintlify/writer

Comments URL: https://news.ycombinator.com/item?id=31946963

Points: 2

# Comments: 0

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Wed, 15 Jun 2022 15:07:03 +0000

Agreed!

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Wed, 15 Jun 2022 14:48:05 +0000

That's an incredibly good piece of feedback. Working on it now

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Wed, 15 Jun 2022 14:43:55 +0000

Excellent suggestion. We're gonna work this into the product for sure

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Wed, 15 Jun 2022 00:51:47 +0000

Totally agreed. While the frontend and core functions are open source, the backend under the `server` folder is source available. We made the mistake of referring to the entire repo as open source, which we will refrain from in the future.

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Tue, 14 Jun 2022 23:46:04 +0000

We totally agree! We think it would be best when documentation is centralized, version controlled, and coupled with the code. Unfortunately, we realized that's just not the case for the vast majority of companies. One way to think about our product is just bringing the features of documentation on GitHub into existing documentation that lives outside of it.

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Tue, 14 Jun 2022 21:49:33 +0000

That is correct. The backend covers enterprise features that are only source-available, whereas the rest of the application is open source. We understand that this can be quite misleading, and will refrain from saying that we are open source in the future

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Tue, 14 Jun 2022 21:16:19 +0000

Thank you for sharing the article! We definitely don't see companies having all docs in their repos, but strongly believe that there should be stronger ties between docs and code (and more transparency in docs in general)

It's a really hard problem to solve, but we believe that there will be a product that will crack it (even if it's not what we have right now)

New comment by hanyiwang in "Launch HN: Mintlify (YC W22) – Maintainable documentation for software teams"

hanyiwang — Tue, 14 Jun 2022 18:11:30 +0000

Thank you so much for the incredible feedback! We think you are absolutely SPOT ON. We would really love to chat more with you 1:1. Please reach out to us at han@mintlify.com