You're not wrong, but you can use that technique and benefit from Dependency CI too. Typically, you can define your dependencies in a file specific to a certai

You're not wrong, but you can use that technique and benefit from Dependency CI too. Typically, you can define your dependencies in a file specific to a certain package manager. NPM uses `package.json`, RubyGems uses `Gemfile`, etc. It is a reasonable practice to "vendor in" your dependencies, as you suggest. But given the declaration of your dependencies in some manifest file, Dependency CI can give you valuable insights.