Skip to content

Main content

Development: Package Manager Integrity Token Split Tool

Split one restricted sha256/384/512 integrity token into algorithm and Base64 digest text; does not verify digest bytes, algorithm length or package integrity.

Loading tool…

Description

Split a restricted package-integrity token.

Integrity metadata describes an algorithm and expected bytes or an object-ID prefix. Recognizing its written shape is separate from computing a digest, verifying content or establishing the uniqueness of an abbreviated object name.

Split a restricted package-integrity token.

When to use this tool

Use Development: Package Manager Integrity Token Split when inspecting an integrity-related token without accessing its content.

How to use the tool and how it works

  1. Enter token. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Split a restricted package-integrity token. Accept sha256/sha384/sha512, a hyphen and Base64-looking digest with up to two trailing equals signs and length divisible by four.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultReturned object; expand its named members below.Required. Object.
result.algorithmAlgorithmCalculated result member: string.
result.digestBase64Shape-checked Base64 text; digest bytes, required hash length and canonical pad bits are not verified.Calculated result member: string.
json
{
  "input": {
    "token": "sha256-YWJj"
  },
  "output": {
    "result": {
      "algorithm": "sha256",
      "digestBase64": "YWJj"
    }
  }
}

Limitations and assumptions

  • This checks token shape, not digest size, canonical pad bits, file bytes or cryptographic integrity.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use a suitable cryptographic implementation or Git repository lookup to verify bytes, identity and uniqueness.

References

  1. Calculation and input contract: development/package-manager-integrity-token-split — tool.io

Similar or alternative tools