Tags (Labels)

Tag	Meaning
section	Pages that form the main sections of this standard and that are listed in the Section Index on the SEI CERT C Coding Standard page.
links-to-void	Guidelines with links to a rule in 6 The Void. The link should be removed.
update-checker	Guidelines that have been significantly changed since the checker was coded. The checker needs updating.
incomplete	Pages that need work.
deleteme	Pages that need to be deleted. See also void below.
citations-incomplete	Pages that have problems with the citations at the bottom.
sidebar	Pages with comments that might make good sidebars.
exportable-c	Guidelines in other CERT secure coding standards (residing in other Wiki spaces) that might make good C guidelines. Port to C those rules that are truly applicable.
exportable-java	Guidelines that might be candidates for adoption in the SEI CERT Oracle Coding Standard for Java.
void	Pages tagged for elimination from the standard and that are listed in 6 The Void.

ROSE-Specific Tags (Labels)

Pages now have tags (also known as

Wiki Markup
{doc://display/DOC/Working with Labels Overview}Labels{doc}

) to indicate the status of their corresponding checker in Compass Rose:

Tag	Meaning
rose-complete	ROSE catches all violations
rose-partial	ROSE catches some violations
rose-possible	ROSE could catch some or all violations, but doesn't yet.
rose-gcc	ROSE doesn't catch violations, but will soon, `GCC` catches violations
unenforceable	These rules can't be checked automatically.
rose-nonapplicable	These rules could be checked automatically in theory, but not by ROSE.
rose-na-macros	ROSE could check these rules if it recognized macro usage.
rose-na-multiple-files	ROSE could check these rules if it operated on multiple files at once.
rose-false-positive	ROSE could enforce this rule, but could not avoid catching some false positives.

At this point, all rules should have one of these tags. That is, they should be completely or partially checked by ROSE, or they should be marked 'rose-possible', in that we will try to check them with ROSE, or they should have one of the nonapplicable tags indicating we don't think they can be checked with ROSE.

...

It might also be worth giving these another look.

STR34-C. Ensure that source and destination pointers in function arguments do not point to overlapping objects

ARR34-C. Ensure that array types in assignment expressions are compatible

FLP33-C. Prevent decimal errors when converting from integers to floating point numbers

MSC08-A. Library functions should validate their parameters

EXPxx-A. Always use sizeof operator to retrieve datatype sizes

Do not use vfork(2)

DAN30-A. Create a copy constructor and assignment operator for non copyable objects

MSC31-C. Ensure return values are compared against the proper type

INT14-A. Avoid pointer to integer and integer to pointer conversions

MSC05-A. Do not make assumptions about the type of time_t and clock_t