op-js
shell-plugins
op-js | shell-plugins | |
---|---|---|
9 | 6 | |
89 | 491 | |
- | 2.6% | |
7.8 | 8.7 | |
3 months ago | 2 days ago | |
TypeScript | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
op-js
-
Optimize Your Git Setup: Strategies for Handling Multiple GitHub Accounts
To get started with the 1Password CLI, visit the official 1Password CLI documentation. Here, you'll find installation guides, usage examples, and how to integrate it with various tools and workflows, including Git and SSH authentication.
-
Join the 1Password Hackathon hosted by Hashnode and compete for $10,000 in prizes
1Password CLI: Automate administrative tasks, securely provision secrets across development environments, and use biometrics to authenticate in the terminal.
-
1Password CLI, AWS and Terraform
1Password CLI is great, having a single source for managing access keys and being able to use fingerprint ID on a Mac is such a cool feature. The AWS plugin works great, but if you want to use AWS through a third party (in this case Terraform), I failed to get it to work.
-
(In)Security of the “Pass” password manager
I know it's not FOSS but 1Password does have a decently fully-featured CLI client
https://developer.1password.com/docs/cli/
- Last Pass Replacement
-
What's in my RC 2022
I used to be anti hosted password managers, but I was recommended using 1password and their CLI client to manage my passwords.
-
Automate GitHub API Calls With Ruby, Keyboard Maestro, and 1Password CLI
When a customer emails me to request access, all I have to do is copy their username from the email they sent me, then I press ⌃-⌥-⌘-A, and it's done! This automation uses Keyboard Maestro, the GitHub API, and 1Password CLI.
-
How to use 1Password to share local secrets
The 1Password CLI. You can find the installation docs here.
-
Introducing 1Password for Visual Studio Code
VS Code extensions run in a Node environment, and we wanted to interact with the new CLI. So we built and open-sourced an entirely new package for doing exactly this: op-js. It wraps the CLI with a simple-to-use JavaScript interface and ships with TypeScript declarations, making 60+ commands, including those that support biometrics unlock, available to your Node-based application.
shell-plugins
-
End of Life for Twilio Authy Desktop App
Consider 1Password, with the added bonus of the `op` CLI tool and a variety of other dev conveniences.
CLI: https://developer.1password.com/docs/cli/get-started/
Shell plugins: https://developer.1password.com/docs/cli/shell-plugins
Secrets automation: https://developer.1password.com/docs/secrets-automation
-
Join the 1Password Hackathon hosted by Hashnode and compete for $10,000 in prizes
1Password Shell Plugins: Eliminate API access keys stored on disc and securely authenticate any CLI with your fingerprint, Apple Watch, or other biometrics.
-
1Password to Add Telemetry
I often regret any contact I have with the Bitwarden fanbase, because whooo they are rabid, but I guess I used to be a rabid fan of 1P so maybe fair's fair :-D Anyway ...
- https://github.com/bitwarden/clients/issues/1620 was created 2021, after it was migrated from the issue that was open even longer in the other repo, and now they've locked the issue because they're tired of people complaining about the extension losing their credentials
- there are a ton more Item types in 1Password, which some people consider just cosmetic ("you can create your own fields") but https://bitwarden.com/help/managing-items/ compared to https://support.1password.com/item-categories/ is night and day, setting aside the native support for SSH agent that's built into 1P nowadays
and here starts the list of even more highly subjective items, which I acknowledge are highly subjective
- the folder based item management in Bitwarden is highly inferior to the tags based management in 1P. Creating folders itself is a major PITA, whereas creating tags in 1P is ... just type the new tag name. Maybe people enjoy putting the "tags" in there item's names or whatever, and doing away with folders in Bitwarden, but ... the fact they're trying to implement tagging on the cheap indicates they want tags but Bitwarden doesn't see the world that way
- I find the attachment management process cumbersome in Bitwarden, whereas in 1P there are actually two orthogonal ways of managing attachments: they can be first class Items (called "Document" items) meaning that is the whole secret that one would care about, and they can also be arbitrarily attached to other Items in kind of a supporting role. I have scans of my passport attached to the Passport item type because so many places ask me to upload a scan of my passport. Same for my driver's license on the formal Driver's License item type
- in the theme of "finding it cumbersome," I find that 1Password seems to care a lot more about UX than Bitwarden. Now, of late I am having to qualify any such statement because yikes that 1P 8 rewrite was catastrophic. But, rewrite-induced-self-inflicted-harm aside, I still think 1P cares a lot more about UX than Bitwarden
- also subjective, but I really enjoy the `op run` <https://developer.1password.com/docs/cli/reference/commands/...> and its ability to resolve specially formatted env-vars <https://developer.1password.com/docs/cli/secret-references> in the sub-process. That process seems to be the basis of their shell plugins system <https://developer.1password.com/docs/cli/shell-plugins> but TBH I find just having env-vars lying around to be more convenient than their shell plugin system for my workflow. The fact that the `op` binary is smart enough to use DBus to auth to my desktop session means I can also use it as an implementation of pinentry
A perfectly reasonable question may be "well, it's open source, why not start fixing bugs?" The things about using folders and the lack of item types indicates to me that they're just rowing in a different direction than what I would like, and the fact that they're a commercial company means unless I directly would benefit from fixing a bug means I am not incentivized to contribute free labor
- 1Password Shell Plugins
-
Secretlint 6: masking API tokens in .bash_history and .zsh_history
Credentials are often stored as raw text in .config/ or ~/.aws. These can be found in 1Password Shell Plugins, op run, zenv, envchain, etc. to avoid storing raw tokens in files.
-
Use Your Fingerprint with 1Password to Authenticate the Twilio CLI
You can find the code for the shell plugins on this GitHub repo.
What are some alternatives?
convertkit-ruby - A Ruby gem that wraps the ConvertKit API v3
plugin-webhook - Twilio CLI plugin to emulate webhook requests from Twilio
Octokit - Ruby toolkit for the GitHub API
flex-plugin-builder - Packages related to building a Twilio Flex Plugin
enpass-cli - Enpass commandline client
secretlint - Pluggable linting tool to prevent committing credential.
direnv - unclutter your .profile
plugin-watch - Access and stream your Twilio debugger logs along with your calls and messages.
op-vscode - 1Password for VS Code
dev-phone - A developer tool for testing SMS and Voice applications
rubygems - Library packaging and distribution for Ruby.
zsh-history-substring-search - 🐠 ZSH port of Fish history search (up arrow)