{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihgvjdsujcy6oglr5as22lg6swwbatogek5m764yyesv5tahb3pay",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3miouik5xcqe2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigay3x2qu2chta6d3kjok4k7c5cqq5my74lqzuiz7wh5o4ambwjxy"
    },
    "mimeType": "image/png",
    "size": 76163
  },
  "path": "/post/48247884",
  "publishedAt": "2026-04-03T22:27:56.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Security",
    "codeinabox",
    "5 comments",
    "https://filiphric.com/dont-let-ai-read-your-env-files"
  ],
  "textContent": "submitted by codeinabox to security\n13 points | 5 comments\nhttps://filiphric.com/dont-let-ai-read-your-env-files\n\n> AI coding assistants like Claude Code, Cursor, and GitHub Copilot are becoming part of our daily workflow. They read our files, understand our codebase, and help us write code faster. But there’s a problem - they can also read your .env files.",
  "title": "Don’t let A.I. read your .env files"
}