Ignoring Variables and Files

ignore

Ignore false positives by adding the variable(s) to the .envscanconfig.json rules file.

$ env-guardian ignore variableName

# Output
✔ Now ignoring variableName
✨ Updated ignore config at /path/to/.envscanconfig.json

You can ignore multiple variables at a time.

$ env-guardian ignore variableName anotherVar

# Output
✔ Now ignoring variableName
✔ Now ignoring anotherVar
✨ Updated ignore config at /path/to/.envscanconfig.json

---

ignore-files

Ignore all variables in a file if you know that there is and never will be sensitive values in them.

$ env-guardian ignore-files path/to/file.js

# Output
✔ Now ignoring ALL variables in path/to/file.js
✨ Updated ignore config at /path/to/.envscanconfig.json

You can ignore multiple files at a time.

$ env-guardian ignore-files path/to/file.js another/path/file.ts

# Output
✔ Now ignoring ALL variables in path/to/file.js
✔ Now ignoring ALL variables in another/path/file.ts
✨ Updated ignore config at /path/to/.envscanconfig.json

---

ignore-list

Display a list of all the variables and files you have in your ignore rules

$ env-guardian ignore-list

# Output

🛑 Currently Ignored Rules:

• variableName (globally)
• anotherVar (globally)
• ALL variables in path/to/file.js
• ALL variables in another/path/file.js

If you look at the contents of .envscanconfig.json you can see your rules added.

// Example .envscanconfig.json file contents.
{
  "ignore": {
    "variables": [
      'variableName', 
      'anotherVar'
    ],
    "files": [
      'path/to/file.js', 
      'another/path/typeFile.ts'
    ]
  }
}

---