{
  "dataset_id": "30_hash_functions",
  "title": "Cryptographic Hash Functions",
  "domain": "computer_security",
  "primary_entity_field": "function_name",
  "field_guide": {
    "function_name": "Function Name",
    "digest_bits": "Digest Bits",
    "publication_year": "Publication Year",
    "security_status": "Security Status",
    "design_family": "Design Family",
    "typical_use_note": "Typical Use Note"
  },
  "record_count": 6,
  "records": [
    {
      "record_id": "30_hash_functions_01",
      "function_name": "MD5",
      "digest_bits": 128,
      "publication_year": 1992,
      "security_status": "Broken for collisions",
      "design_family": "Merkle-Damgard",
      "typical_use_note": "Legacy checksums",
      "entity_name": "MD5",
      "summary": "MD5 appears in the Cryptographic Hash Functions dataset with function_name=MD5; digest_bits=128; publication_year=1992; security_status=Broken for collisions; design_family=Merkle-Damgard; typical_use_note=Legacy checksums."
    },
    {
      "record_id": "30_hash_functions_02",
      "function_name": "SHA-1",
      "digest_bits": 160,
      "publication_year": 1995,
      "security_status": "Broken for practical collision resistance",
      "design_family": "Merkle-Damgard",
      "typical_use_note": "Legacy Git object IDs",
      "entity_name": "SHA-1",
      "summary": "SHA-1 appears in the Cryptographic Hash Functions dataset with function_name=SHA-1; digest_bits=160; publication_year=1995; security_status=Broken for practical collision resistance; design_family=Merkle-Damgard; typical_use_note=Legacy Git object IDs."
    },
    {
      "record_id": "30_hash_functions_03",
      "function_name": "SHA-256",
      "digest_bits": 256,
      "publication_year": 2001,
      "security_status": "Currently strong for general use",
      "design_family": "SHA-2",
      "typical_use_note": "TLS, certificates, blockchains",
      "entity_name": "SHA-256",
      "summary": "SHA-256 appears in the Cryptographic Hash Functions dataset with function_name=SHA-256; digest_bits=256; publication_year=2001; security_status=Currently strong for general use; design_family=SHA-2; typical_use_note=TLS, certificates, blockchains."
    },
    {
      "record_id": "30_hash_functions_04",
      "function_name": "SHA3-256",
      "digest_bits": 256,
      "publication_year": 2015,
      "security_status": "Currently strong for general use",
      "design_family": "Sponge",
      "typical_use_note": "FIPS 202 standard family member",
      "entity_name": "SHA3-256",
      "summary": "SHA3-256 appears in the Cryptographic Hash Functions dataset with function_name=SHA3-256; digest_bits=256; publication_year=2015; security_status=Currently strong for general use; design_family=Sponge; typical_use_note=FIPS 202 standard family member."
    },
    {
      "record_id": "30_hash_functions_05",
      "function_name": "BLAKE2b",
      "digest_bits": 512,
      "publication_year": 2012,
      "security_status": "Currently strong for general use",
      "design_family": "HAIFA-inspired",
      "typical_use_note": "Fast software hashing",
      "entity_name": "BLAKE2b",
      "summary": "BLAKE2b appears in the Cryptographic Hash Functions dataset with function_name=BLAKE2b; digest_bits=512; publication_year=2012; security_status=Currently strong for general use; design_family=HAIFA-inspired; typical_use_note=Fast software hashing."
    },
    {
      "record_id": "30_hash_functions_06",
      "function_name": "RIPEMD-160",
      "digest_bits": 160,
      "publication_year": 1996,
      "security_status": "Legacy but still seen in some ecosystems",
      "design_family": "MD-like",
      "typical_use_note": "Some cryptocurrency address pipelines",
      "entity_name": "RIPEMD-160",
      "summary": "RIPEMD-160 appears in the Cryptographic Hash Functions dataset with function_name=RIPEMD-160; digest_bits=160; publication_year=1996; security_status=Legacy but still seen in some ecosystems; design_family=MD-like; typical_use_note=Some cryptocurrency address pipelines."
    }
  ]
}