Sample work · Code & Bugs
Dependency Audit: Project versions, vulnerabilities, and licenses checked
A demo project with fictitious packages: unspecified versions, packages with vulnerabilities, a package with an incompatible license, an unknown package. Findings by severity with suggestions, the after-list exists.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Pin versions, report vulnerabilities below the fixed version
- Package license checked against project license
- Unknown packages are identified, not silently accepted
- Packages and operation are fictitious
Download requirements-vorher.txt Download requirements-nachher.txt
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Demo project with six packages: Before 5 findings (vulnerabilities, license, unspecified, unknown), After 0
- Advisory database with fictitious packages, offline
- 9 checks
Limits
What this sample does not cover, so nobody expects more:
- Only knows vulnerabilities listed in the connected database
- License assignment is technical, no legal advice
- Updates are only adopted with the customer project's tests
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.