Release 2.1.0#10
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 29427053 | Triggered | Generic Password | 1c6b392 | tests/test_config_analyzer.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
There was a problem hiding this comment.
Pull request overview
This PR prepares the 2.1.0 release by updating package versions, adding confidence/fixture filtering controls, improving analyzer resilience, and expanding analyzer coverage/tests.
Changes:
- Adds minimum-confidence and fixture inclusion options across CLI, bridge, scanner, and VS Code integration.
- Adds analyzer runtime isolation and SARIF version reporting from package metadata.
- Refines secrets/PII/config/dependency analyzers and updates documentation/tests for the release.
Reviewed changes
Copilot reviewed 24 out of 25 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
vscode-src/pythonBridge.ts |
Passes confidence and fixture options to the Python bridge. |
src/contractguard/scan.py |
Adds filtering, runtime-error findings, timestamps, and scan target options. |
src/contractguard/cli.py |
Exposes confidence/fixture options in CLI commands. |
src/contractguard/bridge.py |
Exposes confidence/fixture options in bridge commands. |
src/contractguard/reporter.py |
Uses package version in SARIF output. |
src/contractguard/analyzers/file_filters.py |
Adds shared fixture/source/data/doc/ignore/size helpers. |
src/contractguard/analyzers/secrets_analyzer.py |
Reduces false positives and adds confidence-aware secret findings. |
src/contractguard/analyzers/pii_analyzer.py |
Tightens PII matching and adds confidence-aware direct findings. |
src/contractguard/analyzers/dependency_analyzer.py |
Adds pyproject/npm parsing and advisory handling. |
src/contractguard/analyzers/config_analyzer.py |
Adds config filtering and refined SSL/default-password detection. |
src/contractguard/analyzers/json_analyzer.py |
Skips package/config JSON files not intended as samples. |
src/contractguard/__init__.py |
Bumps Python package version to 2.1.0. |
tests/test_* |
Adds coverage for analyzer filtering, confidence, runtime errors, and version reporting. |
README.md |
Documents release capabilities and configuration additions. |
CAPABILITIES.md |
Updates advertised scanner and dependency capabilities. |
DEPLOYMENT.md |
Updates packaging/runtime notes. |
INSTRUCTIONS.md |
Adds confidence-related usage examples. |
pyproject.toml |
Bumps Python project version. |
package.json |
Bumps extension version and adds configuration/package updates. |
package-lock.json |
Updates lockfile release metadata and dependency entry. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| for name, version in poetry_deps.items(): | ||
| if name.lower() != "python": | ||
| dependencies.append(f"{name}=={version}" if isinstance(version, str) else name) |
| ## Notes | ||
|
|
||
| - The extension runs analysis locally. | ||
| - The default minimum confidence is `medium`; use `low` for audit mode when you want sample/test fixtures included. |
|
|
||
| for source, content in files: | ||
| facts = extract_facts_from_requirements(content) | ||
| facts = extract_facts_from_dependency_file(source, content) |
No description provided.