AI Slop Code Risk Monitor

eggert/tz

SlopCodeMonitor badge for eggert/tz Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Time zone database and code

3.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for eggert/tz, a C project with 1,926 GitHub stars. SynthScan examined 15,320 lines of code across 14 source files, recording 57 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 3.3 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

3.3
Adjusted Signal
3.3
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
1.9K
Stars
C
Language
15.3K
Lines of Code
14
Files
57
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 15.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 57 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 17.5/100 · LOW

Which changes need focused human review? 57 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 1LOW 56

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 57 distinct pattern matches across 2 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block56 hits · 48 pts
SeverityFileLineSnippetContext
LOWzdump.c21#ifndef HAVE_LOCALTIME_RZCOMMENT
LOWlocaltime.c21COMMENT
LOWlocaltime.c41#endifCOMMENT
LOWlocaltime.c61COMMENT
LOWlocaltime.c81# endifCOMMENT
LOWlocaltime.c201# define IINNTT_MAX LONG_MAXCOMMENT
LOWlocaltime.c221# define CLOCK_MONOTONIC_COARSE CLOCK_MONOTONICCOMMENT
LOWlocaltime.c261 to support the offtime or mktime variant. */COMMENT
LOWlocaltime.c281# ifdef TM_GMTOFFCOMMENT
LOWlocaltime.c301COMMENT
LOWlocaltime.c321# define O_PATH 0COMMENT
LOWlocaltime.c341# if defined __GLIBC__ && 2 < __GLIBC__ + (19 <= __GLIBC_MINOR__)COMMENT
LOWprivate.h61# ifndef _FILE_OFFSET_BITSCOMMENT
LOWprivate.h101/* This string was in the Factory zone through version 2016f. */COMMENT
LOWprivate.h121# define HAVE__GENERIC (201112 <= __STDC_VERSION__)COMMENT
LOWprivate.h141#ifndef HAVE_INCOMPATIBLE_CTIME_RCOMMENT
LOWprivate.h161#ifndef HAVE_STRDUPCOMMENT
LOWprivate.h181# endifCOMMENT
LOWprivate.h241COMMENT
LOWprivate.h261#ifndef ENOTCAPABLECOMMENT
LOWprivate.h301# endifCOMMENT
LOWprivate.h321#endifCOMMENT
LOWprivate.h341#endifCOMMENT
LOWprivate.h381# ifndef HAVE_INTTYPES_HCOMMENT
LOWprivate.h401# ifndef INT_FAST64_MAXCOMMENT
LOWprivate.h421COMMENT
LOWprivate.h441# endifCOMMENT
LOWprivate.h461# define PRIdMAX "ld"COMMENT
LOWprivate.h481# endifCOMMENT
LOWprivate.h521# endifCOMMENT
LOWprivate.h541# define ckd_sub(r, a, b) __builtin_sub_overflow(a, b, r)COMMENT
LOWprivate.h561#if HAVE___HAS_C_ATTRIBUTECOMMENT
LOWprivate.h581# define ATTRIBUTE_FALLTHROUGH __attribute__((fallthrough))COMMENT
LOWprivate.h601# if __has_c_attribute(noreturn)COMMENT
LOWprivate.h621# define ATTRIBUTE_REPRODUCIBLE /* empty */COMMENT
LOWprivate.h641# define ATTRIBUTE_PURE ATTRIBUTE_REPRODUCIBLECOMMENT
LOWprivate.h661#define ATTRIBUTE_PURE_114833_HACK ATTRIBUTE_PURE_114833COMMENT
LOWprivate.h701*/COMMENT
LOWprivate.h721# define difftime tz_difftimeCOMMENT
LOWprivate.h741# define posix2time tz_posix2timeCOMMENT
LOWprivate.h761# define tzalloc tz_tzallocCOMMENT
LOWprivate.h781# undef daylightCOMMENT
LOWprivate.h821 || defined __GLIBC__ || defined __tm_zone /* musl */ \COMMENT
LOWprivate.h841# elseCOMMENT
LOWprivate.h881** declarations if time_tz is defined.COMMENT
LOWprivate.h921# define TM_GMTOFF tm_gmtoffCOMMENT
LOWprivate.h941time_t mktime_z(timezone_t restrict, struct tm *restrict);COMMENT
LOWprivate.h1061# ifndef timeoffCOMMENT
LOWprivate.h1081# ifndef unreachableCOMMENT
LOWstrftime.c81 && (/* OpenBSD 5.5 (2014-05-01) and later has 64-bit time_t. */ \COMMENT
LOWzic.c21#ifndef O_BINARYCOMMENT
LOWzic.c41COMMENT
LOWzic.c61# include <sys/random.h>COMMENT
LOWzic.c101static mode_t creat_perms = CREAT_PERMS;COMMENT
LOWzic.c161#if __STDC_VERSION__ < 201112 || defined __SUNPRO_CCOMMENT
LOWzic.c761 (TYPE_SIGNED(mode_t) \COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMworkman.sh4# This file is in the public domain, so clarified as ofCOMMENT