whatisgithub

What is secretstore?

powershell/secretstore — explained in plain English

Analysis updated 2026-08-03 · repo last pushed 2026-06-22

185C#Audience · ops devopsComplexity · 2/5MaintainedSetup · easy

In one sentence

PowerShell SecretStore keeps passwords and API keys encrypted on your own computer so scripts can retrieve them securely instead of hardcoding sensitive data in plain text.

Mindmap

mindmap
  root((repo))
    What it does
      Encrypts secrets locally
      Password-protected unlock
      Attach metadata to secrets
    Tech stack
      PowerShell
      C#
      Cross-platform
    Use cases
      Database credentials in scripts
      Cloud API keys for automation
      Avoid hardcoding secrets
    Audience
      IT professionals
      System administrators
      PowerShell scripters
    Status
      Feature complete
      Security fixes only
      Winding down

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Store database credentials that a PowerShell script retrieves at runtime instead of hardcoding them.

USE CASE 2

Keep cloud service API keys encrypted locally so automation scripts can pull them securely.

USE CASE 3

Save sensitive tokens with metadata notes so teammates know what each secret is for.

What is it built with?

PowerShellC#.NET

How does it compare?

powershell/secretstoremaxifan/tunnelxql-win/quicklook.plugin.officeviewer-native
Stars185184189
LanguageC#C#C#
Last pushed2026-06-222025-06-15
MaintenanceMaintainedStale
Setup difficultyeasymoderateeasy
Complexity2/53/52/5
Audienceops devopsdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Install as a PowerShell module and optionally configure a password timeout, no external infrastructure required.

This is a Microsoft project, the license is not specified in the explanation, so check the repository for exact terms.

So what is it?

PowerShell SecretStore is a tool that lets you keep passwords, API keys, and other sensitive information right on your own computer in an encrypted file. It is designed for people who write PowerShell scripts and need a secure place to stash secrets instead of leaving them in plain text or pasting them directly into scripts. When you save a secret, it gets encrypted and written to a file tied to your user account. The data stays encrypted even while sitting in memory, and is only decrypted at the moment you ask for it back. By default, it requires a password to unlock, you type it once, and it stays unlocked for a configurable window (15 minutes by default) before asking again. You can also attach metadata to secrets, like notes about what they are for. The main audience is IT professionals, system administrators, and anyone writing PowerShell automation. For example, if you have a script that connects to a database or a cloud service, you can retrieve the needed credentials from the store at runtime instead of hardcoding them. It works across Windows, Linux, and macOS. For automated jobs where a human is not around to type a password, you can configure it to run without prompting, though that mode is less secure because the decryption key lives in a local file. One notable thing is that the PowerShell team has declared this project feature complete and is winding it down. They point out that the landscape has shifted toward passwordless authentication, passkeys, biometrics, single sign-on, and hardware security keys, which the current design cannot meaningfully support. They will still fix security issues, but no new capabilities are planned. This makes it a solid choice for existing PowerShell workflows that need simple, local secret storage, but not something to build long-term plans around if you are starting fresh.

Copy-paste prompts

Prompt 1
Write a PowerShell script that stores an API key in SecretStore, then retrieves it at runtime to authenticate against a REST API endpoint.
Prompt 2
Set up PowerShell SecretStore so that an unattended scheduled task can retrieve secrets without prompting for a password, and explain the security tradeoff.
Prompt 3
Create a PowerShell function that accepts a secret name, retrieves the value and its metadata from SecretStore, and returns both to the caller.
Prompt 4
Migrate hardcoded passwords in an existing PowerShell script to use SecretStore instead, showing before and after code.

Frequently asked questions

What is secretstore?

PowerShell SecretStore keeps passwords and API keys encrypted on your own computer so scripts can retrieve them securely instead of hardcoding sensitive data in plain text.

What language is secretstore written in?

Mainly C#. The stack also includes PowerShell, C#, .NET.

Is secretstore actively maintained?

Maintained — commit in last 6 months (last push 2026-06-22).

What license does secretstore use?

This is a Microsoft project, the license is not specified in the explanation, so check the repository for exact terms.

How hard is secretstore to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is secretstore for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.