brycx / checkpwn Goto Github PK

colored relies on atty which is unsound and also seems as if it's unmaintained. Let's see if colored (colored-rs/colored#122) moves away from this, and if not, how else we should handle this.

dirs is unmaintained. dirs-next is the follow-up.

Hi,

I'm building a password checker, and this seems to be the right piece of code I would ned, but it is a binary rather than a library. Are there any chances it can turn to a library, too?

The API key that was previously being kindly donated by a user, is no longer valid. Thus, test-calls that rely on this fail. I don't use this part of the API so I won't be buying a new key to re-enable testing of this.

If anyone wants this tested, feel free to get in touch.

Consider adding Hudson Rock's complimentary data to receive additional intelligence about email address that was compromised in global Infostealer attacks.

Email sample: https://cavalier.hudsonrock.com/api/json/v2/osint-tools/[email protected]

Free API key and full documentation is available here: https://cavalier.hudsonrock.com/docs

Thank you.

HIBP is moving to a paid version of its account API, which means that you now need to purchase an API key to make calls to its API (See the blogpost here). I will most likely not be purchasing such a key and will therefor not be able to test any features adding this.

If anybody is interested in this feature being added and willing to provide an API key for this, I would be willing to implement it.

The change to the commercial API does not affect the password API. In other words, you may still check for breached passwords with checkpwn pass.