hurtmongoose

bert base detect jailbreak

Classify & tag

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text classificationLicense: apache-2.0SHA-256 recorded for 6 of 9 filessafetensors · BIN
Quick answer: compatibility and sources

Can I run bert-base-detect-jailbreak on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

bert-base-detect-jailbreak is an open-weights language model for text classification. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: 51de9d65c5ca34331de309f901b6a88363a87c5cceeb8c9f7de0feee989fc1ef. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

Key facts

Catalog record
Summarizes upstream metadata; it is not itself a download or run receipt.
File evidence
Lists exact filenames, availability and any recorded SHA-256 for individual files.
Run evidence
Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
Checksum scope
SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

Evidence you can inspect (plain text)

  • This page’s quick answer names the file record for hf-model-hurtmongoose-bert-base-detect-jailbreak.
  • Open /artifact/hf-model-hurtmongoose-bert-base-detect-jailbreak/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-hurtmongoose-bert-base-detect-jailbreak for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-hurtmongoose-bert-base-detect-jailbreak/card.md for machine-readable source facts (not a runtime test).
  • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • File availability check:
  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.

Requirements and source record
hurtmongoose/bert-base-detect-jailbreak

Content controls: not assessed.

The catalog lists this model for sorting text into categories. Catalog sources: license, cardMetadata.license, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors438 MB
51de9d65…989fc1ef51de9d65c5ca34331de309f901b6a88363a87c5cceeb8c9f7de0feee989fc1ef
Download availability is being checked.File metadata
training_args.bin5.43 KB
c3be4239…a0ac1e58c3be4239126fd695ab9c25c159b49fdeba1fdaa66b89619d9259c089a0ac1e58
Download availability is being checked.File metadata
Tokenizer & config
config.json687 bytes
480be562…54510932480be5620ad6828024a85978d01f42a03e5f9c8006f18d7f39b057ce54510932
Download availability is being checked.File metadata
special_tokens_map.json125 bytes
b6d346be…76237ee3b6d346be366a7d1d48332dbc9fdf3bf8960b5d879522b7799ddba59e76237ee3
Download availability is being checked.File metadata
tokenizer.json711.7 KB
0d3aef59…3997d9630d3aef594edd5f9b53e7f814277a9171dc70ff93eb66bda6e01f7aa53997d963
Download availability is being checked.File metadata
tokenizer_config.json1.22 KB
1f92c93d…c72d5d771f92c93d2e31974acffab86d48e80a9357acb18c68346c5472ef1d12c72d5d77
Download availability is being checked.File metadata
vocab.txt231.5 KB—Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md2.85 KB—Download availability is being checked.File metadata

Check a download

In the folder where you saved config.json, run:

macOS
shasum -a 256 -- 'config.json'
Linux
sha256sum -- 'config.json'
Windows
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.