Repository Analysis

openssl/openssl

General purpose TLS and crypto library

2.5 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of openssl/openssl, a C project with 30,454 GitHub stars. SynthScan v2.0 examined 1,379,753 lines of code across 2983 source files, recording 2663 pattern matches distributed across 12 syntactic categories. The overall adjusted score of 2.5 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

2.5
Adjusted Score
2.5
Raw Score
100%
Time Factor
2026-07-14
Last Push
30.5K
Stars
C
Language
1.4M
Lines of Code
3.0K
Files
2.7K
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 0MEDIUM 457LOW 2206

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 2663 distinct pattern matches across 12 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Over-Commented Block2149 hits · 1928 pts
SeverityFileLineSnippetContext
LOWConfigurations/shared-info.pl1#! /usr/bin/env perlCOMMENT
LOWConfigurations/gentemplate.pm341 # libraries (they end up in @foreign_objs). We get the latter any timeCOMMENT
LOWcrypto/LPdir_unix.c41#include <limits.h>COMMENT
LOWcrypto/armcap.c1/*COMMENT
LOWcrypto/armcap.c21#ifdef _WIN32COMMENT
LOWcrypto/armcap.c81#elif defined(__ANDROID_API__)COMMENT
LOWcrypto/armcap.c121#endifCOMMENT
LOWcrypto/armcap.c141#define OSSL_HWCAP_CE_SHA1 (1 << 5)COMMENT
LOWcrypto/mem_sec.c41#endifCOMMENT
LOWcrypto/mem_sec.c61#if defined(SYS_mlock2)COMMENT
LOWcrypto/ppccap.c1/*COMMENT
LOWcrypto/ppccap.c21#if !defined(__power_set)COMMENT
LOWcrypto/ppccap.c81 if (OPENSSL_ppccap_P & PPC_MFTB)COMMENT
LOWcrypto/ppccap.c121#ifndef AT_HWCAPCOMMENT
LOWcrypto/vms_rms.h21#define FAB_OR_NAML_FNS naml$l_long_filename_sizeCOMMENT
LOWcrypto/vms_rms.h41#else /* def NAML$C_MAXRSS */COMMENT
LOWcrypto/s390xcap.c21#include <sys/stat.h>COMMENT
LOWcrypto/LPdir_win.c41#include "internal/numbers.h"COMMENT
LOWcrypto/init.c1/*COMMENT
LOWcrypto/init.c21#include "crypto/err.h"COMMENT
LOWcrypto/info.c21#include <jitterentropy.h>COMMENT
LOWcrypto/info.c221#ifdef OPENSSL_RAND_SEED_RDCPUCOMMENT
LOWcrypto/o_dir.c21#define LP_find_file_end OPENSSL_DIR_endCOMMENT
LOWcrypto/uid.c41#if __ANDROID_API__ >= 18COMMENT
LOWcrypto/threads_pthread.c21#ifdef REPORT_RWLOCK_CONTENTIONCOMMENT
LOWcrypto/threads_pthread.c41#include <stdbool.h>COMMENT
LOWcrypto/threads_pthread.c61#define TSAN_FAKE_LOCK(x)COMMENT
LOWcrypto/LPdir_vms.c41#include <string.h>COMMENT
LOWcrypto/o_fopen.c21 * without extra "magic" comprise *BSD, Darwin, IRIX...COMMENT
LOWcrypto/provider_core.c1/*COMMENT
LOWcrypto/provider_core.c21#include "crypto/store.h" /* ossl_store_loader_store_cache_flush */COMMENT
LOWcrypto/context.c1/*COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1#! /usr/bin/env perlCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl21# This translator is not designed to convert *arbitrary* assemblerCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl41# ".type name,@abi-omnipotent" instead.COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl161# assembler ML). Using of .previous got introduced to .pl files withCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl181# .text$ SEGMENT ALIGN(256) 'CODE'COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl201# ; stack looks like:COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl601}COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl621 # 3 and describe how to deduce CFA, Canonical Frame Address. ThisCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl921 }COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1481COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1501# %r13 - -COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1521# storage [without allocating a frame]. One can actually argue thatCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1541# endifCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1561# subroutine entry point and return "exception is not handled, keepCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1581# movq -24(%rcx),%rbp # restore non-volatile registersCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1601# { rsp = (ULONG64 *)context->Rsp;COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1621# function's module. In order to do that one has to know members'COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1641# CONTEXT.Rip 248COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1661# .byte 9,0,0,0COMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1681# In case you wonder why references are 32-bit .rvas and not 64-bitCOMMENT
LOWcrypto/perlasm/x86_64-xlate.pl1701# are too subtle to discuss here. For now it's sufficient to say thatCOMMENT
LOWcrypto/perlasm/cbc.pl1#! /usr/bin/env perlCOMMENT
LOWcrypto/perlasm/cbc.pl21COMMENT
LOWcrypto/perlasm/riscv.pm1#! /usr/bin/env perlCOMMENT
LOWcrypto/perlasm/riscv.pm21# are met:COMMENT
LOWcrypto/perlasm/x86asm.pl1#! /usr/bin/env perlCOMMENT
LOWcrypto/perlasm/sparcv9_modes.pl1#! /usr/bin/env perlCOMMENT
LOWcrypto/asn1/a_strex.c1/*COMMENT
2089 more matches not shown…
Decorative Section Separators356 hits · 1148 pts
SeverityFileLineSnippetContext
MEDIUMcrypto/md5/asm/md5-sparcv9.pl10# ====================================================================COMMENT
MEDIUMcrypto/md5/asm/md5-sparcv9.pl17# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-586.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-586.pl15# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-parisc.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-parisc.pl15# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-s390x.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-s390x.pl15# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-c64xplus.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-c64xplus.pl15# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-x86_64.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-x86_64.pl15# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-md5-x86_64.pl10# ====================================================================COMMENT
MEDIUMcrypto/rc4/asm/rc4-md5-x86_64.pl15# ====================================================================COMMENT
MEDIUMcrypto/des/asm/dest4-sparcv9.pl10# ====================================================================COMMENT
MEDIUMcrypto/des/asm/dest4-sparcv9.pl14# ====================================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl313 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl333 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl356 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl439 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl478 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl524 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl591 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl655 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl879 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1002 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1101 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1177 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1239 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1338 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1372 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1398 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1421 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1717 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1731 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1828 # ==============================================================COMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl1855 # ==============================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-alpha.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-alpha.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-ia64.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-ia64.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-parisc.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-parisc.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghashp8-ppc.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghashp8-ppc.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghashv8-armx.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghashv8-armx.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-c64xplus.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-c64xplus.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-armv8-unroll8_64.pl10#========================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-armv8-unroll8_64.pl16#========================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-ppc.pl10#===================================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-ppc.pl43# ===================================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-sparcv9.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-sparcv9.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-x86.pl10# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/ghash-x86.pl15# ====================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-avx512.pl33#======================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-avx512.pl86#======================================================================COMMENT
MEDIUMcrypto/modes/asm/aes-gcm-armv8_64.pl10#========================================================================COMMENT
296 more matches not shown…
Self-Referential Comments47 hits · 159 pts
SeverityFileLineSnippetContext
MEDIUMcrypto/perlasm/riscv.pm2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/md5/asm/md5-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/ml_dsa/asm/ml_dsa_ntt-x86_64.pl15# This file provides optimized x86_64 assembly implementations of the NumberCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64-zvkg.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64-zvkb-zvbc.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/aes-gcm-riscv64-zvkb-zvkg-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/chacha/asm/chacha-riscv64-v-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/ec/asm/x25519-x86_64.pl20# This module implements radix 2^51 multiplication and squaring, andCOMMENT
MEDIUMcrypto/poly1305/asm/poly1305-armv9-sve2.pl12# This file is an SVE2 port-and-merge of POLY1305 hash algorithm, derived fromCOMMENT
MEDIUMcrypto/poly1305/asm/poly1305-ppc.pl17# This module implements Poly1305 hash for PowerPC.COMMENT
MEDIUMcrypto/poly1305/asm/poly1305-armv8.pl17# This module implements Poly1305 hash for ARMv8.COMMENT
MEDIUMcrypto/poly1305/asm/poly1305-sparcv9.pl17# This module implements Poly1305 hash for SPARCv9, vanilla, as wellCOMMENT
MEDIUMcrypto/poly1305/asm/poly1305-ppcfp.pl17# This module implements Poly1305 hash for PowerPC FPU.COMMENT
MEDIUMcrypto/poly1305/asm/poly1305-x86_64.pl17# This module implements Poly1305 hash for x86_64.COMMENT
MEDIUMcrypto/poly1305/asm/poly1305-s390x.pl17# This module implements Poly1305 hash for s390x.COMMENT
MEDIUMcrypto/poly1305/asm/poly1305-x86.pl17# This module implements Poly1305 hash for x86.COMMENT
MEDIUMcrypto/sm3/asm/sm3-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm3/asm/sm3-armv8.pl9# This module implements support for Armv8 SM3 instructionsCOMMENT
MEDIUMcrypto/sm3/asm/sm3-x86_64.pl11# This module implements support for Intel(R) SM3 instructionsCOMMENT
MEDIUMcrypto/sm3/asm/sm3-riscv64-zvksh.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm4/asm/vpsm4-armv8.pl10# This module implements SM4 with ASIMD on aarch64COMMENT
MEDIUMcrypto/sm4/asm/sm4-riscv64-zvksed.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm4/asm/vpsm4_ex-armv8.pl10# This module implements SM4 with ASIMD and AESE on AARCH64COMMENT
MEDIUMcrypto/sm4/asm/sm4-x86_64.pl11# This module implements support for Intel(R) SM4 instructionsCOMMENT
MEDIUMcrypto/sm4/asm/sm4-armv8.pl10# This module implements support for SM4 hw support on aarch64COMMENT
MEDIUMcrypto/sha/asm/sha512-loongarch64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-loongarch64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-riscv64-zvkb-zvknha_or_zvknhb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha512-riscv64-zvkb-zvknhb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha512-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv32-zkn.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aesv8-armx.pl17# This module implements support for ARMv8 AES instructions. TheCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvbb-zvkg-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aesni-x86_64.pl17# This module implements support for Intel AES-NI extension. InCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvkb-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zkn.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aesni-x86.pl17# This module implements support for Intel AES-NI extension. InCOMMENT
MEDIUMcrypto/aes/asm/aesp8-ppc.pl17# This module implements support for AES instructions as per PowerISACOMMENT
MEDIUMtest/certs/mkcert.sh12# This file is dual-licensed and is also available under other terms.COMMENT
MEDIUMtest/recipes/95-test_external_pyca_data/cryptography.sh38# Create a python virtual env and activateCOMMENT
MEDIUMtest/recipes/25-test_eai_data/kdc.sh3# Create a root CA, signing a leaf cert with a KDC principal otherName SAN, andCOMMENT
MEDIUMutil/reformat-patches.sh328# Create the worktreeCOMMENT
MEDIUMutil/ctags.sh74# This file is automatically generated by $0.COMMENT
MEDIUMutil/perl/TLSProxy/Proxy.pm292 # Create the Proxy socketCOMMENT
Slop Phrases35 hits · 98 pts
SeverityFileLineSnippetContext
MEDIUMcrypto/perlasm/riscv.pm2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
LOWcrypto/md5/asm/md5-586.pl115 # make sure to do 'D' first, not 'B', else we clash withCOMMENT
LOWcrypto/md5/asm/md5-586.pl133 # make sure to do 'D' first, not 'B', else we clash withCOMMENT
MEDIUMcrypto/md5/asm/md5-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64-zvkg.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64-zvkb-zvbc.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/ghash-riscv64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/modes/asm/aes-gcm-riscv64-zvkb-zvkg-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/chacha/asm/chacha-riscv64-v-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm3/asm/sm3-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm3/asm/sm3-riscv64-zvksh.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sm4/asm/sm4-riscv64-zvksed.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha512-loongarch64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-loongarch64.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-riscv64-zvkb-zvknha_or_zvknhb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha512-riscv64-zvkb-zvknhb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha512-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/sha/asm/sha256-riscv64-zbb.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv32-zkn.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvbb-zvkg-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvkb-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zvkned.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMcrypto/aes/asm/aes-riscv64-zkn.pl2# This file is dual-licensed, meaning that you can use it under yourCOMMENT
MEDIUMtest/quic-openssl-docker/hq-interop/quic-hq-interop.c26 * @note This client is intended for demonstration purposes and may requireCOMMENT
LOW…es/95-test_external_oqsprovider_data/oqsprovider-ca.sh56# Don't forget to use provider(s) when not activated via config fileCOMMENT
LOWutil/perl/OpenSSL/Util.pm221 # It seems to be an executable, so we make sure to prefix itCOMMENT
MEDIUMdemos/guide/quic-client-block.c115 * is for demonstration purposes only.COMMENT
MEDIUMdemos/guide/quic-client-non-block.c222 * is for demonstration purposes only.COMMENT
MEDIUMdemos/signature/rsa_pss_direct.c22 * Here we sign an all-zeroes digest for demonstration purposes.COMMENT
MEDIUMdemos/digest/EVP_MD_xof.c54 /* Allow digest length to be changed for demonstration purposes. */COMMENT
MEDIUMdemos/cipher/aesgcm.c102 * For demonstration purposes the IV is being set here. In a compliantCOMMENT
MEDIUMdemos/encode/rsa_encode.c17 * output for demonstration purposes. Both public and private keys are accepted.COMMENT
MEDIUMdemos/encode/ec_encode.c17 * output for demonstration purposes. Both public and private keys are accepted.COMMENT
MEDIUMdemos/mac/poly1305.c60 * purely for demonstration purposes. Please note that Poly1305 exhibitsCOMMENT
LOWdemos/quic/poll-server/quic-server-ssl-poll-http.c1538 * adjust _want_events, don't forget to ask poll manager to rebuildCOMMENT
AI Slop Vocabulary26 hits · 81 pts
SeverityFileLineSnippetContext
MEDIUMcrypto/x86cpuid.pl235# Essentially there is only one use for this function. Under DJGPP:COMMENT
MEDIUMcrypto/perlasm/x86_64-xlate.pl1667# To facilitate composing of .pdata structures, auto-generated "gear"COMMENT
MEDIUMcrypto/rc4/asm/rc4-md5-x86_64.pl22# below theoretical maximum, interleaving them would allow to utilizeCOMMENT
MEDIUMcrypto/modes/asm/aes-gcm-avx512.pl171# ; helps to facilitate SEH handlers writing.COMMENT
LOWcrypto/modes/asm/aes-gcm-riscv64-zvkb-zvkg-zvkned.pl441 # Note: The actual vl should be `FULL_BLOCK_LEN32/4 * 2`, but we just useCOMMENT
MEDIUMcrypto/chacha/asm/chacha-s390x.pl36# But to harness overheads revert to transliteration of VSX code pathCOMMENT
MEDIUMcrypto/chacha/asm/chacha-s390x.pl436# On the other hand minimum amount of data it takes to fully utilizeCOMMENT
MEDIUMcrypto/poly1305/asm/poly1305-mips.pl38# The return value is placed in $a0. Following coding rules facilitateCOMMENT
MEDIUMcrypto/bn/asm/mips-mont.pl40# The return value is placed in $a0. Following coding rules facilitateCOMMENT
MEDIUMcrypto/sha/asm/sha512-mips.pl42# The return value is placed in $a0. Following coding rules facilitateCOMMENT
MEDIUMcrypto/sha/asm/keccak1600-armv8.pl35# instructions effectively facilitate parallel hashing, which we don'tCOMMENT
MEDIUMcrypto/sha/asm/sha1-armv4-large.pl731 # this fix-up provides Thumb encoding in conjunction with INSTCOMMENT
MEDIUMcrypto/sha/asm/sha1-x86_64.pl25# capacity to fully utilize SHA-1 parallelism. Therefore this freshCOMMENT
MEDIUMcrypto/sha/asm/sha1-mips.pl40# The return value is placed in $a0. Following coding rules facilitateCOMMENT
MEDIUMcrypto/sha/asm/keccak1600-avx2.pl26# It makes other steps more intricate, but overall, is it a win? To beCOMMENT
MEDIUMcrypto/aes/asm/aesv8-armx.pl4104 // After specially processing, utilize the five blocks processing again.COMMENT
MEDIUMcrypto/aes/asm/aesni-sha1-x86_64.pl23# utilize processor resources better and achieve better performance.COMMENT
MEDIUMcrypto/aes/asm/aesni-sha1-x86_64.pl65# fully utilize parallelism, so stitching would not give any gainCOMMENT
MEDIUMcrypto/aes/asm/aesni-sha256-x86_64.pl23# utilize processor resources better and achieve better performance.COMMENT
MEDIUMcrypto/aes/asm/aes-mips.pl53# The return value is placed in $a0. Following coding rules facilitateCOMMENT
MEDIUMtest/run_tests.pl50 # compatibility with the /proc paradigm.COMMENT
MEDIUMtest/run_tests.pl415# If this isn't a TAP::Parser::Aggregator, it's the pre-TAP test harness,COMMENT
MEDIUM…cipes/95-test_external_oqsprovider_data/oqsprovider.sh81# Be verbose if harness is verbose:COMMENT
MEDIUMutil/perl/OpenSSL/Util.pm197 # Prefix to be applied as needed. Essentially, we need to determineCOMMENT
LOWutil/perl/TLSProxy/NextProto.pm49# For now though since we don't support parsing we just create an empty NextProtoCOMMENT
MEDIUM.github/workflows/ct-validation-daily.yml24# harness and fails the job.COMMENT
Fake / Example Data17 hits · 23 pts
SeverityFileLineSnippetContext
LOWtest/quic_fifd_test.c97static const unsigned char placeholder_data[] = "placeholder";CODE
LOWtest/certs/setup.sh431NC="excluded;otherName:SRVName;UTF8STRING:foo@example.org" ./mkcert.sh genca \CODE
LOWtest/certs/setup.sh438 "otherName.1 = SRVName;UTF8STRING:foo@example.org"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt418Output = "lorem ipsum dolor sit amet"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt418Output = "lorem ipsum dolor sit amet"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt451Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt456Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt461Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt466Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt471Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt476Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt481Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt631Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt636Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt641Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt646Output = "lorem ipsum"CODE
LOWtest/recipes/30-test_evp_data/evppkey_rsa_common.txt651Output = "lorem ipsum"CODE
Redundant / Tautological Comments12 hits · 18 pts
SeverityFileLineSnippetContext
LOWcrypto/sm3/asm/sm3-riscv64-zbb.pl336 # Decrement length by 1COMMENT
LOWcrypto/sm3/asm/sm3-riscv64-zvksh.pl386 bnez $NUM, L_sm3_loop # Check if there are any more block to processCODE
LOWcrypto/bn/asm/riscv64-mont.pl1040 # Check if we have processed all elements of a:COMMENT
LOWcrypto/sha/asm/sha512-loongarch64.pl289 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha256-loongarch64.pl295 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha256-riscv64-zvkb-zvknha_or_zvknhb.pl149 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha512-riscv64-zvkb-zvknhb.pl158 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha512-riscv64-zvkb-zvknhb.pl330 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha512-riscv64-zbb.pl230 # Decrement length by 1COMMENT
LOWcrypto/sha/asm/sha256-riscv64-zbb.pl305 # Decrement length by 1COMMENT
LOWtest/slhdsa_parse.py60 # Check if there is a similar test already and skip if soCOMMENT
LOWexternal/perl/Text-Template-1.56/lib/Text/Template.pm655 # Print result text instead of returning itCOMMENT
Structural Annotation Overuse10 hits · 15 pts
SeverityFileLineSnippetContext
LOWcrypto/bn/asm/ppc.pl268# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl406# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl834# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl988# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1527# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1578# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1624# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1740# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1782# NOTE: The following label name should be changed toCOMMENT
LOWcrypto/bn/asm/ppc.pl1888# NOTE: The following label name should be changed toCOMMENT
Deep Nesting5 hits · 5 pts
SeverityFileLineSnippetContext
LOWtest/mlkem_parse.py45CODE
LOWtest/mldsa_wycheproof_parse.py34CODE
LOWtest/mldsa_wycheproof_parse.py71CODE
LOWutil/acvp-test.py312CODE
LOWutil/acvp-test.py586CODE
Unused Imports3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtest/slhdsa_parse.py26CODE
LOWtest/mldsa_wycheproof_parse.py26CODE
LOWtest/cms-msg/make_missing_kdf_der.py16CODE
Excessive Try-Catch Wrapping2 hits · 2 pts
SeverityFileLineSnippetContext
LOWutil/acvp-test.py1108 except Exception as exc:CODE
LOWutil/acvp-test.py1168 except Exception:CODE
Verbosity Indicators1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcrypto/LPdir_unix.c68 * small value (HP-UX offers 14), so we need to check if we got a result, andCOMMENT