Repository navigation
Release v12.9.3
This 12.x maintenance release backports the fixes for one high-severity security advisory from #4880, which ships in 13.9.0. Users who can move to @cdxgen/cdxgen 13.9.0 get these fixes along with the medium and low severity fixes that are not backported to 12.x.
Security
- GHSA-qp92-6qfc-m3qp: scanned content could make cdxgen run project tooling, a gpg program or project code although installs were off. The
.npmrcgate now recognises every spelling npm accepts, refusesglobalandprefix, and replaces a project's proxy and TLS settings with the operator's own for the install.packageManagercan select only npm, yarn or pnpm. The rush and pipenv installs, the pip tree recovery and the pregen npm install followinstallDepsand its secure-mode default, as does cdxi.create. The piptree helper no longer imports modules from the scanned repository, go.sum names cannot becomego mod whyoptions, release-note and commit-log reads no longer run a repository's signature verifier or gpgsm, and git metadata is read only from the scanned tree's own repository.
Upgrade notes
- The rush and pipenv installs no longer run with
--no-install-deps. - A project
.npmrcthat setsproxy,https-proxy,cafile,caorstrict-sslno longer applies to the automatic npm install; the operator's settings or npm's defaults do, with a warning. - Reference clones,
--separate-git-dirand a.gitsymlink lose git metadata unlessCDXGEN_GIT_ALLOW_EXTERNAL_GITDIR=true. - The 12.x workflows are now listed in
.github/workflows/actions.lock.
The issues were found by Anthropic's OSS Scanner (scan cdxgen-20261117-013).
Full Changelog: v12.9.2...v12.9.3