internal structure of a batch name

Coppie di cifre seguite da un carattere alfanumerico a fine stringa

matches anime filenames. such as Group] Name [Episode[Audiometa]others.ext supports NCOP, NCED, OP, ED, SP, SPnn, nn, nn.n, nn.n_vn mp4, mkv, srt, ass but you could add more. the episode must be written within a [] bracket. finally, this regex cannot cover all the cases and obviously have some issues, but it's fine under most cases. it is also a small regex practice for me.

This is a GitHub Advanced Security (GHAS) Secret Scanning Custom Pattern I created to detect likely hardcoded credentials while reducing common false positives in code. Goal: detect assignments for these key names: password secret apikey / api_key / api-key Pattern regex: (?i)\b(password|secret|api[-]?key)\b\s[:=]\s(?!\s\$\{)(?!\sprocess\.env\b)(?:['"])?[A-Za-z0-9!@#$%^&()+=-]{5,}(?:['"])? What it should catch (examples): password: "ahsjdfahsjfhdjsahj" secret = 'kjfskahfsdhfj' apikey: ABCDE12345!@# (unquoted) What it tries NOT to catch (common false positives): password: ${password_somename} (template/variable placeholder) secret: ${VAULT_SECRET} password: process.env.DB_PASSWORD (env var reference, not a hardcoded secret) This is intended as a practical baseline; it won’t be perfect for every language/config style. If you have suggestions to improve the detection accuracy (reduce false positives/false negatives) for GHAS custom patterns, please share.

Finds CSS selectors that only contain one line and, using the substitution, flattens everything to be on the same line.

Matches and verifies IP address. 192.168.0.1 Matches 999.999.9.9 Didn't match

52 character long regex to validate IP address.

selects numbers, with commas and decimals, like 1,234.56

Grabs the outer parentheses and contents taking into account inner parentheses enclosures

matches composer packages with -alpha, -beta and -rc versionings

Regex showing how to match the five parts in an OmegaT project name (named as per the internal convention at cApStAn), including labels for each captured group (each part in the name).

match: #aabbcc #abc (255,255,255) (255,255,255,255) 255,255,255 no match: #gggggg #ggg 256,256,256

Selects the ` and ` tags from a string. You can probably do this with something easier, but this works

Regex for Door_Double

ตรวจสอบพยัญชนะต้น (ต้องมี) ตรวจตัวสะกดสำหรับสระที่ต้องมี ตรวจสอบการวางสระและวรรณยุกต์ไทย หมายเหตุ การตรวจสอบตัวสะกดในภาษาไทยตรวจสอบได้ยากเพราะภาษาไทยเป็นภาษาที่เขียนติด ๆ กันไม่มีการแบ่งคำอย่างชัดเจนทำให้การอ่านภาษาไทยผู้อ่านต้องใช้ความหมายของคำในการตัดสินการอ่านแบ่งคำตามความเหมาะสมเช่นคำว่า "ตากลม" อาจอ่านเป็น "ตาก-ลม" ก็ได้ หรืออ่านเป็น "ตา-กลม"ก็ได้ ดังนั้นการเขียน Regex เพื่อทำการตรวจสอบอาจช่วยได้ระดับหนึ่ง อ่าจมีผิดบ้างถูกบ้าง แต่ก็ถือว่าเป็นเครื่องมือที่ใช้ช่วยเหลือในการตรวจสอบเพิ่มเติมได้ 80% ของความเป็นไปใด้ก็แล้วกันนะครับ หวังว่าการเขียนเพิ่มเติมส่วนนี้ จะมีประโยชน์บ้างไม่มากก็น้อย

This regular expression provides a balance between RFC compliance and security-best-practices. It is designed to prevent injection vectors in legacy systems by using a restricted "safe" character subset recommended by the OWASP Validation Regex Repository. Pattern: ^A-Za-z0-9(?:\.A-Za-z0-9_+&-]+)*@(?:[A-Za-z0-9{0,61}[A-Za-z0-9])?\.)+[A-Za-z]{2,63}$ Key Features: Forced Alphanumeric Start: Prevents leading hyphens to avoid command injection vulnerabilities. Security Subset: Restricts special characters to _+&*- to prevent exotic character injections (e.g., pipes or backticks). No Quoted Strings: Forbids quoted strings to eliminate dangerous payloads containing spaces or backslashes. DNS Compliance: Enforces label lengths (1–63 characters) and prevents labels from starting or ending with hyphens. Whole String Anchoring: Uses ^ and $ to ensure the entire input is validated.

Extracts the following fields from a Laravel Log print: Time Stamp (Date) Log Level (supports optional prefix (ie. local.DEBUG)) Log Message Exception | Context If an exception is detected, the file reference (file path + line number), and optional stacktrace are captured.

Correct Poland PESEL base regex validator. Covers birth dates up to 2099 year. PESEL numbers are in YYMMDDXXXXX format, however, the month is adjusted based on what year people were born. People born from 1900-1999 has no adjustment, 2000-2099 is the month +20, 2100-2199 is +40, 2200-2299 is +60. For example, if someone was born December 16, 2016, their PESEL would be 163216XXXXX.

PLF4

PLF3

PLF2

plf1

hey das ist richtig coool oder?

This is a Python RE for matching different parts and combinations of various docker/container image references, as compatible with docker pull etc. Parts / Capture Groups image: # whole image repo: # everything but the tag/digest registry: # host+port host: port: name: # path within registry reference: # tag or digest (with : or @; I haven't bothered to figure out how to strip that yet) tag: digest: If it matches, it should match image, repo, and name at the very least.

Simple prefix matcher for validating URI Schemes according to [RFC2396, Section 3.1]( http://www.faqs.org/rfcs/rfc2396.html#3.5:~:text=well%20as%20%22http%22%29.-,scheme%20%20%20%20%20%20%20%20%3D%20alpha%20*%28%20alpha%20%7C%20digit%20%7C%20%22%2B%22%20%7C%20%22%2D%22%20%7C%20%22.%22%20%29,-Relative%20URI%20references) Go Playground: https://go.dev/play/p/vtYEugsNAfo

URL, URI format validation

Used to check Email Format

ตรวจสอบการใช้วรรณยุกต์และสระในภาษาไทย รองรับการใช้สระอาาาาาติดกันแบบลากเสียง ไม่ตรวจสอบพยัญชนะต้นและตัวสะกด

ใช้ตรวจสอบวรรณยุกต์และสระในภาษาไทย ไม่ตรวจสอบพยัญชนะต้นและตัวสะกด

Matches instagram urls for posts, reels, and stories works on all flavors except rust

match every type of discord url with each useful part in a group pretty optimized, shouldnt be too harsh on your system should work in every flavor except rust because rust sucks lol

I've created this for a simple project of mine, it squishes every book of the Bible into a RegEx, with the full name, abbreviation, and abbreviation with a dot. Then, it matches the chapter and verse relatively simply.

Flagged / disallowed text expression used in cApStAn's build of OmegaT

Custom tags expression used in cApStAn's build of OmegaT

Caculator seperator with groups

Basic Regex for CSS Selector. Pseudo-Elements, Combinators and other advanced stuff are not supported.

Extracts HP Prime PPL numbers.

Extracting strings defined in languages like C/C++ etc.

554

Format validation for U.S. phone numbers with or without a country code and with various formatting and punctuation permissible.

AoC 2025 Day 5 part 1 but also works for part 2. You just don't need the IDs at the bottom for part 2

Search string for use in contact cleaning project $1 = intenational code, omitting preceding "+" $2 = area code $3 = first three digits of phone number $4 = last four digits of phone $5 = extension, inclusive of any commas or hashes to automate phone tree navigation TO DO handle recursive menus (e.g., "321-321-1234,,,1234#,,123344#....)

Search for the occurence of the 3 following words: CHA, LOG and TAG. Should be in the above order sequence (but it also if works swapped).

``/^(?P0|1-9]\d)\.(?P0|[1-9]\d)\.(?P0|[1-9]\d)(?:-(?P(?:0|[1-9]\d|\d[a-zA-Z-)(?:\.(?:0|1-9]\d|\d[a-zA-Z-))))?(?:\+(?P[0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$/gmsAD

Extract field value of DoubleQuote Enclosed CSV Field with Escaped DoubleQuote The matching field value still contains escaped double quotes to be later processed :-)

test

Overview This Regular Expression shows any text between HTML tags or between quotation marks within the tags themselves. An example would be: <HTML lang="en", then selecting the 'en' from there. Group 1 is between tags, and group 2 is in the quotes. I recommend only using half of this regular expression, like the 'between tags' part, or the 'inside quotes part'. Explanation The whole regex is built of two alternates, the tags and quotes part. The tags part (the first part) starts with a lookbehind of a closing of a tag, then a lazy part that selects almost characters, and a lookahead that checks for the beginning of tag (so the text is between tags). The quotes part is built in a similar structure, where it looks behind for an open of a tag, .+ , then checking for an equals sign followed by a quotation mark. The middle section of the quotes part is again just searching for text, but also not including quotation marks. The lookahead checks for a closing quotation mark and that's it! Please comment any questions or email me.

Fixwithpecra

for Problem 2 - Fancy Barcodes

One of the regular expressions I use for my plugin Title Cleaner OST.