[Feature Request] Strict mode

Open
  • Is something wrong?
#165 0 comments 0 reactions 2 assignees View on GitHub

Maintainers usually reply within 1 day

@theoephraim is already working on this.

Since Oct 8, 2025.

Assessment

This issue has not been assessed yet.

Description

enhancement
Description

It would be good to have a "strict" or "high security" mode that disallows all @sensitive values on disk, even in non-tracked env files.

Motivation

Allows policy enforcement for high security orgs and certain regulatory environments.

Proposed Solution

Validation check in load and run that will give a validation error if any @sensitive values are present on disk.

Alternatives

No response

Additional Information

Some challenges:

  • a user can change the local copy of their schema
Dominant language
TypeScript
Stars
4.9k
Forks
140
Avg merge
2d 3h
Merged PRs (30d)
35

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dmno-dev/varlock

All issues in dmno-dev/varlock

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.