Security model
A product about environment risk has to be careful about environment data.
EnvPI is designed to understand enough to help without defaulting to full secret-value storage. The product is built around metadata-first handling, visible provenance, and explicit boundaries so you can understand what is being analyzed, what is being redacted, and what remains outside the core system.
Understand the reference, not just the raw value
The point of EnvPI is not to become a careless dumping ground for sensitive data. Its job is to build an operationally useful record of environment-linked assets: what exists, where it came from, what project or environment it belongs to, what vendor it appears tied to, and when an external issue might matter.
In practical terms, that means the system helps you long before it needs to behave like a traditional vault.
What EnvPI is designed to keep
- Variable names and labels
- Project and environment relationships
- Vendor associations
- Dependency relationships
- Source provenance
- Findings, recommendations, and resolution history
- Handling metadata such as timestamps, status, and confidence
What EnvPI avoids by default
- Full raw secret-value storage as the primary operating model
- Invisible ingestion of sensitive content
- Ambiguous boundaries between local analysis and uploaded data
- Generic "trust us" language without visible handling rules
How .env ingestion works
When you import a .env source, the process makes handling visible. The product parses the source, identifies likely references, shows what metadata will be captured, and makes redaction obvious before anything is persisted. You get a reviewable boundary, not a black box.
How repository scanning works
Repository scanning focuses on evidence building: references, dependency manifests, configuration patterns, likely exposures, and provenance. The goal is not to silently ingest everything possible. The goal is to provide enough structured context to support reliable findings and next-step recommendations.
How local scanning works
Local analysis emphasizes hygiene and visibility, especially around ignored files, duplicated references, and workspace sprawl. You can see what the local scanner examines, what remains local, and what signals become part of the evidence record.
Trust comes from visible boundaries
A product like EnvPI earns trust by making its decisions inspectable. You can see where a finding came from, what evidence supports it, which source introduced the relevant fact, and what assumptions were made along the way. Provenance is not only useful for debugging the system. It is part of the trust model.
Security principles
Minimum necessary data
Explicit handling boundaries
Visible provenance
Reviewable ingestion
Clear local versus remote behavior
A product architecture that respects user caution
Frequently asked questions
Read the model, then try it on one project.
The best way to evaluate EnvPI is to connect a small, understandable part of your stack and see what evidence it builds.