Skip to main content

Overview

Cysmiq parses dependency manifests and lock files to identify packages and match them against vulnerability advisories. This page lists supported file types by ecosystem.

Supported file types

JavaScript / TypeScript

Package ManagerManifestLock File
npmpackage.jsonpackage-lock.json
Yarnpackage.jsonyarn.lock
pnpmpackage.jsonpnpm-lock.yaml

Python

Package ManagerManifestLock File
piprequirements.txt-
Poetrypyproject.tomlpoetry.lock
PipenvPipfilePipfile.lock
PDMpyproject.tomlpdm.lock
uvpyproject.tomluv.lock

Go

Package ManagerManifestLock File
Go modulesgo.modgo.sum
depGopkg.tomlGopkg.lock

Java / Kotlin

Package ManagerManifestLock File
Mavenpom.xml-
Gradlebuild.gradle, build.gradle.ktsgradle.lockfile
Gradle (settings)settings.gradle, settings.gradle.ktssettings-gradle.lockfile

.NET

Package ManagerManifestLock File
NuGetpackages.config-
NuGet (central)Directory.Packages.props, Packages.props-
NuGet-packages.lock.json
NuGet (generated)-project.assets.json, *.deps.json
Paket-paket.lock

PHP

Package ManagerManifestLock File
Composercomposer.jsoncomposer.lock

Ruby

Package ManagerManifestLock File
BundlerGemfileGemfile.lock

Rust

Package ManagerManifestLock File
CargoCargo.tomlCargo.lock

Elixir / Erlang

Package ManagerManifestLock File
Mixmix.exsmix.lock
Rebarrebar.configrebar.lock

Swift

Package ManagerManifestLock File
Swift Package ManagerPackage.swiftPackage.resolved

Notes

  • Lock files provide precise version information for transitive dependencies
  • When a lock file is present, Cysmiq uses it for version resolution where supported
  • Some ecosystems (pip with requirements.txt, Maven) don’t use lock files by default
  • Some .NET inputs are generated outputs used for dependency resolution