Dependencies
18 items tagged with "dependencies"
Standards2
SemVer 2.0.0
Semantic Versioning (SemVer) is essential for software migrations, providing a clear framework for versioning that helps teams manage changes effectively. By understanding SemVer's principles and implementing robust compliance strategies, teams can mitigate risks, improve dependency management, and facilitate clear communication throughout the migration process.
Perl 5.38 Syntax
Adhering to Perl standards during software migrations is crucial for ensuring code compatibility, maintaining best practices, and streamlining the transition process. By conducting thorough code audits, implementing robust testing protocols, and utilizing effective tools, teams can navigate the complexities of migration with confidence and achieve successful outcomes.
Anti-Patterns2
Reinventing the Wheel
Building from scratch a solved, well-supported capability — like crypto, date handling, or an ORM — instead of using a proven, maintained library or standard.
Dependency Hell
A tangle of conflicting, version-pinned, or transitive dependencies that makes upgrading or even installing software fragile, slow, and unpredictable.
Generators1
FAQs6
What does the scan command analyze?
The scan analyzes: runtime versions (Node.js, .NET, Python, Java, Go, Rust, PHP, Ruby, and more), framework versions (React, Next.js, Angular, Vue, Ne...
What is an SBOM (software bill of materials)?
An SBOM is a formal, machine-readable inventory of all components, libraries, and dependencies that make up a piece of software, including their versi...
What is software supply-chain security?
Software supply-chain security protects the integrity of everything that goes into building and delivering software: source code, third-party dependen...
What does the vg why command do?
`vg why <package>` traces a dependency through your git history: who added it, every version change since, and who made each one. If your latest `vg s...
What does the vg bisect command do?
`vg bisect <package> <constraint>` pinpoints the commit where a dependency crossed a version line. Where `vg why` narrates every version change, `vg b...
Can vg bisect fail my build until a dependency is patched?
Yes. Add `--assert`: `vg bisect lodash 4.17.21 --assert` exits non-zero when the current version does not satisfy the constraint, so a CI step blocks ...
Glossaries6
Software Drift
Software drift is the growing gap between the dependencies, runtimes, and frameworks a codebase actually uses and their current, supported versions.
DriftScore
DriftScore is Vibgrate’s 0–100 measure of maintainability drift — how far a stack has moved from current, supported baselines — where 0 is fully current and 100 is maximum drift.
Libyear
A libyear is the calendar time between the dependency version you use and the latest stable release — a simple, ecosystem-comparable measure of dependency freshness.
Lockfile
A lockfile records the exact, resolved version of every dependency in a project — direct and transitive — so installs are reproducible and the true dependency set is auditable.
Code Drift
Code drift is how far a codebase — and the AI writing in it — has moved away from current, correct, well-understood truth: current versions, correct APIs, and an accurate picture of the code's own structure.
Dependency Drift
Dependency drift is the growing gap between the dependency versions a project declares and the current, supported releases of those same packages.