CVE and update status of the FreeBSD ports tree3,295 unaddressed CVEs in 670 portsAll times are CET
Port details

devel/py-dodgy 0.2.1_1

Search for dodgy looking lines in Python code

0
unaddressed
0
VuXML only
0
fixed
0
open problem reports

Port info

Maintainer
sunpoet@FreeBSD.org
Packages
latest: 0.2.1_1
Upstream
up to date
Last update
to 0.2.1_1 · 2f5d059ad6
Quarterly
2026Q4: 0.2.1_1
WWW
https://github.com/landscapeio/dodgy
Links
cgit · VuXML

Install

Package
# pkg install py312-dodgy
installs 0.2.1_1 from latest; from quarterly (2026Q4) 0.2.1_1
Port
# cd /usr/ports/devel/py-dodgy && make install clean
Size
11 KiB download · 26 KiB installed
Depends on
lang/python312 3.12.15
License
MIT

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 160.2.1_10.2.1_1–
FreeBSD 150.2.1_10.2.1_1–
FreeBSD 140.2.1_10.2.1_10.2.1_1

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 150.2.1_10.2.1_1–
FreeBSD 140.2.1_10.2.1_10.2.1_1

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 0.2.1_1.

Fixed (0)

No VuXML entries for this package.

Problem reports (0) · open in Bugzilla, most recently changed first

None.

Commits (3)

Po-Chuan Hsieh (sunpoet) · 0.2.1_1
devel/py-dodgy: Convert to USE_PYTHON=pep517

- Bump PORTREVISION for package change
2f5d059ad6
Rene Ladan (rene) · 0.2.1
all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>
3d9a815d9c
Po-Chuan Hsieh (sunpoet) · 0.2.1
devel/py-dodgy: Add py-dodgy 0.2.1

Dodgy is a very basic tool to run against your codebase to search for "dodgy"
looking values. It is a series of simple regular expressions designed to detect
things such as accidental SCM diff checkins, or passwords or secret keys hard
coded into files.

While this is primarily aimed at open source projects (for whom a publicly
available secret key is pretty dangerous), it can also be used in private
projects, with the caveat that it will point out things which are not a problem
for private projects and is not configurable enough currently to change that.

Another note - this tool is probably best run pre-commit, since it will
hopefully prevent dodgy things being checked in. To automatically execute before
a commit use a git pre-commit hook.
dad043a777