Public Advisory Reference Age Tool

Description

Inspect supplied public-advisory provenance dates without fetching alerts or inferring threat levels.

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.

Inspect supplied public-advisory provenance dates without fetching alerts or inferring threat levels.

When to use this tool

Use it for public advisory reference age when the required inputs and conventions are already available.

How to use the tool and how it works

Enter publishedDate, retrievedDate, evaluationDate. Use the stated units and boundary conventions.
Run the calculation. Correct any input error before interpreting a result.
Read publicationAgeDays, retrievalAgeDays, retrievalLagDays. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Validate exact ISO calendar dates with publication no later than retrieval and retrieval no later than evaluation. Return publication age, retrieval age, and publication-to-retrieval lag in whole days.^[1]

Input field	Meaning and units	Accepted input
publishedDate	Published Date	Required. Text; maximum UTF-16 length 8192.
retrievedDate	Retrieved Date	Required. Text; maximum UTF-16 length 8192.
evaluationDate	Evaluation Date	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
publicationAgeDays	Publication Age Days	Required. Safe integer.
retrievalAgeDays	Retrieval Age Days	Required. Safe integer.
retrievalLagDays	Retrieval Lag Days	Required. Safe integer.

json

{
  "input": {
    "publishedDate": "2024-01-01",
    "retrievedDate": "2024-01-03",
    "evaluationDate": "2024-01-08"
  },
  "output": {
    "publicationAgeDays": 7,
    "retrievalAgeDays": 5,
    "retrievalLagDays": 2
  }
}

Limitations and assumptions

The dates are supplied provenance, not verified publication history. No advisory is fetched, threat level inferred, or operational action recommended.
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 public advisory reference age, 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

Calculation and input contract: security-studies/public-advisory-reference-age — tool.io

Similar or alternative tools

Advisory Publication Lag
Compare supplied public advisory timestamps without evaluating threats or recommending operational action.
Advisory Version Order Token
Compare advisory tokens under an explicit order without guessing vendor version semantics.