Code security check: secrets scan, dependency audit, Git setup by Gilbert LosertCode security check: secrets scan, dependency audit, Git setup by Gilbert Losert
Code security check: secrets scan, dependency audit, Git setupGilbert Losert
Cover image for Code security check: secrets scan, dependency audit, Git setup
You find out what is exposed in your repository before someone else does. Pick one of the four checks per order.
Deliverables (one of these)
Secrets scan: findings with file and line, values masked in the report, plus a .gitignore and .env.example
Dependency and license audit: versions pinned, known vulnerabilities listed, package licenses compared with yours, unknown packages named
Git workflow setup: branch strategy, merge rules, worktree script, pull request template
Prompt-injection check for an AI skill or plugin: every file read, findings by severity with file, verdict install or do not install
How it works
You send the repository (read access) or the skill folder and name the check.
Everything is checked in writing; nothing from the target is installed or executed.
You receive the report and the generated files.
What you provide
Read access to the code. For Git setup, your hosting service and team size.
Limits
The scan finds known key formats, not freely chosen passwords. Only the account owner revokes found keys. The audit knows vulnerabilities from its connected database and the license mapping is technical, not legal advice. Branch protection is set by you in your host; you get the list. Rewriting history needs a separate agreement.
Starting at$160
Duration4 days
Tags
ai skills
code review
dependency audit
git workflow
license check
prompt injection
repository
secrets scan
security
Service provided by
Gilbert Losert Vienna, Austria
Code security check: secrets scan, dependency audit, Git setupGilbert Losert
Starting at$160
Duration4 days
Tags
ai skills
code review
dependency audit
git workflow
license check
prompt injection
repository
secrets scan
security
Cover image for Code security check: secrets scan, dependency audit, Git setup
You find out what is exposed in your repository before someone else does. Pick one of the four checks per order.
Deliverables (one of these)
Secrets scan: findings with file and line, values masked in the report, plus a .gitignore and .env.example
Dependency and license audit: versions pinned, known vulnerabilities listed, package licenses compared with yours, unknown packages named
Git workflow setup: branch strategy, merge rules, worktree script, pull request template
Prompt-injection check for an AI skill or plugin: every file read, findings by severity with file, verdict install or do not install
How it works
You send the repository (read access) or the skill folder and name the check.
Everything is checked in writing; nothing from the target is installed or executed.
You receive the report and the generated files.
What you provide
Read access to the code. For Git setup, your hosting service and team size.
Limits
The scan finds known key formats, not freely chosen passwords. Only the account owner revokes found keys. The audit knows vulnerabilities from its connected database and the license mapping is technical, not legal advice. Branch protection is set by you in your host; you get the list. Rewriting history needs a separate agreement.
$160