Description
Compare advisory tokens under an explicit order without guessing vendor version semantics.
Security records often depend on explicit counts, clock origins, status flags, and provenance dates. Checking their internal arithmetic can reveal a bookkeeping gap while leaving the underlying evidence and operational decisions for separate review.
Compare advisory tokens under an explicit order without guessing vendor version semantics.
When to use this tool
Use it for advisory version order token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter first, second, suppliedOrder. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read firstKnown, secondKnown, order. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Locate first and second tokens in a distinct suppliedOrder list. Return known flags and sign(secondIndex-firstIndex) only when both are known; otherwise return order zero.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Text; maximum UTF-16 length 8192. |
| second | Second | Required. Text; maximum UTF-16 length 8192. |
| suppliedOrder | Supplied Order | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| firstKnown | First Known | Required. Boolean. |
| secondKnown | Second Known | Required. Boolean. |
| order | Order | Required. Safe integer. |
{
"input": {
"first": "v2",
"second": "v3",
"suppliedOrder": [
"v1",
"v2",
"v3"
]
},
"output": {
"firstKnown": true,
"secondKnown": true,
"order": 1
}
}Limitations and assumptions
- Zero order can mean equality or an unknown token, so inspect both known flags. This is exact token ranking rather than parsing semantic or vendor version strings.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For advisory version order token, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Advisory Publication Lag
Compare supplied public advisory timestamps without evaluating threats or recommending operational action.
- Public Advisory Reference Age
Inspect supplied public-advisory provenance dates without fetching alerts or inferring threat levels.