Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Env var loading and validation for 1Password (open source!)
If you are using 1Password to manage any dev/application secrets, you might be interested in our open source tool - https://varlock.dev We just released a new update that introduces a plugin system and our first plugin is for 1Password (of course) - see https://varlock.dev/plugins/1password/ Our tool lets you define a .env.schema file, which can contain decorator style comments to add additional metadata to your env. This is then used to do validation, generate types, etc. The tool also introduces a new function call syntax, and while you can talk to any external cli using the exec() function, the new 1Pass plugin also adds a new op() function which fetches items from 1Password. So how is this different from using `op run`? Uses the SDK and service account tokens for deployed environments, and (optionally) uses op CLI for local dev (with biometric auth via the desktop app) Adds validation and coercion Automatic type generation (right now just for TypeScript, more to come) Understands which items are sensitive, and adds leak detection when possible Supports loading multiple env-specific files (.env.local, .env.production, etc) Supports explicit imports to break up files however you like Drop in integrations for many frameworks You can also use Varlock alongside the new https://developer.1password.com/docs/environments/ by syncing your environment to a local file (such as `.env.local`) and varlock will automatically load those values, and apply its validation on top. Would love for y'all to take a look, and to hear what you think! Oh and please give us a ⭐ on GitHub @ https://github.com/dmno-dev/varlock --- An example .env.schema file using the new 1Password pluginIntroducing 1Password SDKs for Desktop Integrations
We’re excited to announce new authentication capabilities in the 1Password SDKs! Developers can now build integrations that authenticate directly through the 1Password desktop app using the same trusted methods users already know —Touch ID, their account password, or other supported options. 🏗️ What this unlocks: Native and seamless integrations: Build integrations that connect directly with the 1Password desktop app using the SDK. It’s a secure, native way to integrate with 1Password — no extra setup or dependencies required. Human-in-the-loop workflows: Enable user-scoped authentication in your integrations to support secure, approval-based workflows that keep users in control. Easy to build and adopt: Simplifies integration setup and makes authentication effortless for end users. Now available in public beta for macOS and Linux in the SDKs for Go, JavaScript, and Python. Video not displaying? Watch it here. 💬 Share feedback, get swag We’d love to hear how this feature performs in your integrations — is it reliable and easy to use in your workflows? What would you like to see next? 📖 Read the docs to get started 🧢 The first 10 developers to share feedback on the 1Password Developer Community Hub by November 30th will receive exclusive 1Password swag. Be sure to tag your post with #beta-sdk-desktop-integrations.📣 - Local App Authentication in the SDKs
Hi all, Just wanted to drop a quick note about the updated SDKs for Python, Go and Javascript. We recently introduced another beta enabling desktop applications to request an item from 1Password and then 1Password presents an authentication to the end user. Learn more here 👉 https://developer.1password.com/docs/sdks/desktop-app-integrations What do you all think about this? How is it going for you? Have you had a chance to give it a try? Here's a quick video, I recorded introducing the idea and giving a quick example of it in action! Let us know what you think! Thanks! Phil & the 1Password Team! Video not displaying? Watch it here.
