Checksum Record Width Audit
Audit exact checksum-record integer values against an explicit unsigned bit width; report range failures while rejecting malformed integer spellings.
Description
Audit exact checksum-record integer values against an explicit unsigned bit width; report range failures while rejecting malformed integer spellings.
A checksum record may be numerically outside its declared unsigned width even when its decimal spelling parses. This audit reports such entries individually.
When to use this tool
Audit exact checksum-record integer values against an explicit unsigned bit width; report range failures while rejecting malformed integer spellings.
- Prepare the supplied checksums, bits fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter checksums, bits. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.violations. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require bits from 1 to 128. Parse each checksums string as an exact integer and report entries below zero or at least 2^bits, preserving their source index and original string.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| checksums | checksums. | List of strings; at most 128 entries |
| bits | bits. | Integer from 1 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.violations | Source positions or records that fail the specific screen above; an empty list means no such violation. |
{
"input": {
"checksums": [
"0",
"15",
"16",
"-1"
],
"bits": 4
},
"output": {
"result": {
"violations": [
{
"index": 2,
"value": "16"
},
{
"index": 3,
"value": "-1"
}
]
}
}
}Limitations and assumptions
- Malformed integer strings are input errors. The tool does not compute or authenticate a checksum or verify a payload.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use the complete specified checksum algorithm and independent test vectors when verifying a payload. Field packing, parameter shape and arithmetic agreement are separate checks; none supplies cryptographic authenticity.
References
Similar or alternative tools
- Checksum Hex Width Formatter
Format an exact unsigned checksum as lowercase hex at explicit bit width, enforcing non-nibble-aligned high-bit limits.
- Checksum Hex Width Parser
Parse an exactly width-padded hexadecimal checksum token into exact decimal text, rejecting high bits beyond an explicit non-nibble bit width.