Expired85% confidenceFactTime unknown
Augment's initial security audit found security issues such as API keys being stored directly in the .env.local file and overly permissive CORS configuration.
1
Sources
85%
Confidence
Medium-term (~90 days)
Relevance
6/3/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/1/2026(expired)
Sources
Related Entities
Related Claims
UnverifiedManaging API keys with a .env file rather than hardcoding them is an engineering security best practice that prevents keys from being committed to a Git repository along with the code, causing leakage.70% similarUnverifiedIn BYOK mode, API keys are stored in plaintext in local configuration files, posing a security risk of key leakage68% similarUnverifiedVICE's security scanning covers high-risk issues such as keys leaked in bundled files, Supabase RLS misconfigurations, exposed API endpoints, weak HTTP headers, and infrastructure configurations.66% similarUnverifiedIn CI/CD integration, secure storage of API keys is typically achieved using Vault or environment variable injection66% similarUnverified推荐通过.env文件配合.gitignore排除在本地存储密钥，部署时由云平台Secrets管理服务注入65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/38256API
curl https://kongchang.com/api/v1/knowledge/claims/38256MCP
get_claim(id=38256)