Skip to content

Instantly share code, notes, and snippets.


Mathias Conradt mathiasconradt

View GitHub Profile

Keybase proof

I hereby claim:

  • I am mathiasconradt on github.
  • I am mathiasconradt ( on keybase.
  • I have a public key ASAD35KPmbwd5cC04A3X8dtf1FHj8qm_oIj6FRkUNmeh_Ao

To claim this, I am signing this object:

mathiasconradt /
Created February 18, 2023 23:49 — forked from gboudreau/
Export TOTP tokens from Authy

Generating Authy passwords on other authenticators

There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.

Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon a gist by Brian Hartvigsen. His post had a neat code with it to generate QR codes for you to use on your favorite authenticator.

His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools. If this was not possible, I guess people would be reverse engineering the Android app or something like that. But when I tried that code, nothing appeared on the screen. My guess is that Brian used the

mathiasconradt / snyk.postman_collection.json
Last active February 23, 2023 03:03
Snyk API Postman 2.1 Collection
View snyk.postman_collection.json
"info": {
"_postman_id": "97de3cec-8bcc-4d1f-be6b-30f4e202504e",
"name": "Snyk API",
"description": "The Snyk API is available to customers on [paid plans]( and allows you to programatically integrate with Snyk.\n\n## API vs CLI vs Snyk integration\n\nThe API detailed below has the ability to test a package for issues, as they are defined by Snyk. It is important to note that for many package managers, using this API will be less accurate than running the [Snyk CLI]( as part of your build pipe, or just using it locally on your package. The reason for this is that more than one package version fit the requirements given in manifest files. Running the CLI locally tests the actual deployed code, and has an accurate snapshot of the dependency versions in use, while the API can only infer it, with inferior accuracy. It should be noted that the Snyk CLI has the ability to output machine-readable JSON output (with the `--json` flag to `snyk test`).\n\nA