MCP, MCP server
Copilot Security Instructions
A comprehensive toolkit to guide GitHub Copilot toward secure coding practices.
Compatibility: Not stated.
Grade B
Minor issues only, no Medium or High. Worth a quick look at the findings below before installing.
Not a guarantee. A hygiene check of the source at the commit shown, not a security audit.
SECRETS_PATH_DOTENV OBFUSCATION_FILE_OVER_READ_CAP
Why this grade
- SECRETS_PATH_DOTENV Low
Mentions a .env file.
.gitignore, line 1
.env - OBFUSCATION_FILE_OVER_READ_CAP Note
A file was over the read cap and was not fully read.
package-lock.json, line 1
{
Any High, or two or more Medium findings, give D. One Medium gives C. Low findings or a security Note give B. Each code names a finding behind the letter.
Grades are a hygiene check of the source at the commit shown, on the date checked, not a security audit or a guarantee. The free directory grades are automated. Before release, a PlugVet engineer reviews every paid report and any grade we hold back, including all F grades, against the source code and the evidence we quote.
What was checked
Plain notes from the hygiene checks.
Permissions
Pass
No shell or command execution found, and no extra permission was declared.
Install and update
Pass
No install-time script found, and dependencies are pinned or absent.
Network
Pass
No network call found.
Secrets
Concern
reads a credential or environment file.
SECRETS_PATH_DOTENV
.dockerignore, line 8
.gitignore
.gitignore, line 1
.env
README.md, line 139
cp .env.example .env
Show more
README.md, line 142
The MCP server reads configuration from a `.env` file. Customize the following variables as needed:
copilot-instructions.md, line 10
- Never commit secrets to source control (including `.env` files). Use a secure vault/secret manager (e.g. CyberArk Conjur, Azure Key Vault) and inject secrets at runtime via your
copilot-instructions.md, line 54
- Store secrets in secure vaults or env vars passed through orchestrators - avoid hardcoded strings or `.env` files in prod.
copilot-instructions.md, line 76
- Do not hardcode secrets or API keys - never commit `.env` or use `.env` in production containers.
copilot-instructions.md, line 94
- Do not commit `.env` files or hardcode secrets - use secrets management infrastructure.
Agent instructions
Pass
No instruction to ignore earlier instructions or to hide a step.
Obfuscation
Note
a file was over the read cap and was not fully read.
OBFUSCATION_FILE_OVER_READ_CAP
package-lock.json, line 1
{
Licence
Pass
A licence file is present (LICENSE).
Maintainer activity
Pass
The latest commit is within the last 365 days.
Note
Hygiene check of commit dc2248df23d4. reads a credential or environment file. a file was over the read cap and was not fully read.
Date and source
Date checked:
github.com
Commit graded: dc2248df23d459dfb39a69c27d2d0d92159728db
This link goes to the original host. PlugVet does not host or check what you download from there, and installing it is your own decision and risk.