io.github.irrenwill/secret-safe-env

Name: io.github.irrenwill/secret-safe-env
Author: io.github.irrenwill

MCPcommunity

v0.1.2io.github.irrenwillUnknownUpdated 4mo agonpm GitHub

Write secrets into .env without the agent ever seeing the value - Windows masked dialog (繁中 UI)

讓 agent 把祕密（API key 等）寫進，全程看不到值。agent 呼叫只傳 key 名稱；本機跳出一個原生遮罩對話框，由你貼上祕密，再由 PowerShell 小幫手直接寫入。agent 只收到／／狀態，永遠拿不到值。 Windows + Windows PowerShell 5.1（以釘死路徑啟動） PowerShell 測試需要 Pester 5：在專案的加入（啟動瞬間、不依賴網路）：重載 Claude Code。提供兩個工具：（讓使用者在本機遮罩框輸入 secret 寫進 .env，agent 永不看到值）與（只回 true/false 確認寫入，不回值）。零安裝備援：用（建議釘版本，如）。代價：每次 session 啟動會冷啟動，離線會啟動失敗。值為單行；多行 PEM/JSON 請使用者自行編輯 .env。envpath 請傳專案根的絕對…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1Forks

4mo agoLast update

Package

Authorio.github.irrenwill

LicenseUnknown

Version0.1.2

Sourcemcp-registry

npmsecret-safe-env

GitHubirrenwill/secret-safe-env

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface2 tools · none privileged

Security scan✓ Cleanv0.1.2 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged

Statically extracted from the published packagev0.1.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

set_env_secretNo description published

This tool published no description. Forge does not invent one.

env_key_existsNo description published

This tool published no description. Forge does not invent one.

0 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

io.github.irrenwill/secret-safe-env

Tools

Tools exposed

No dependency coverage