A few days ago, I noticed portaudit telling me about a few things that needed to be updated:

# portaudit
Affected package: rubygem-rails-1.2.3
Type of problem: rubygem-rails — session-fixation vulnerability.
Reference: <http://www.FreeBSD.org/ports/portaudit/30acb8ae-9d46-11dc-9114-001c2514716c.html>
Affected package: rubygem-rails-1.2.3
Type of problem: rubygem-rails — JSON XSS vulnerability.
Reference: <http://www.FreeBSD.org/ports/portaudit/44fb0302-9d38-11dc-9114-001c2514716c.html>
Affected package: rubygem-activesupport-1.4.2
Type of problem: rubygem-rails — JSON XSS vulnerability.
Reference: <http://www.FreeBSD.org/ports/portaudit/44fb0302-9d38-11dc-9114-001c2514716c.html>
3 problem(s) in your installed packages found.
You are […]

Late yesterday, I noticed a couple of sanity test failures. What was interesting about these reports was the lack of an error message. I emailed the committer to let them know I was looking into it.
There were two failures. The first against devel/aunit; the second against devel/florist-gpl.
By the time you read this, […]

The Search and Sanity Test Failure features are now in production. Enjoy.

FreshPorts has a long history of Sanity Testing each commit to the FreeBSD Ports tree. It has been doing this for two main reasons:

Ensure the integrity of the FreshPorts database
Help correct obvious errors as soon as possible

In 2002, FreshPorts allowed committers to opt in to receiving these notifications directly. Prior to this feature, […]

I noticed this today. First, I apologise for highlighting the errors of others, but it is relevant to the topic.
FreshPorts has a number of sanity tests that it performs on each commit to a port. It does simple things like:
make -V PORTVERSION
If an error occurs during any sanity test, FreshPorts records and reports […]