enguard

tiny guard 2m en response refusal binary polyguard

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: mitSHA-256 recorded for 5 of 7 filessafetensors
Quick answer: compatibility and sources

Can I run tiny-guard-2m-en-response-refusal-binary-polyguard 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.

tiny-guard-2m-en-response-refusal-binary-polyguard 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: 5ae052422f86949ca2cc9082c025812a7b948144b841c9f1ccf4e2672e4bb2fe. 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-enguard-tiny-guard-2m-en-response-refusal-binary-polyguard.
  • Open /artifact/hf-model-enguard-tiny-guard-2m-en-response-refusal-binary-polyguard/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-enguard-tiny-guard-2m-en-response-refusal-binary-polyguard for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-enguard-tiny-guard-2m-en-response-refusal-binary-polyguard/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
enguard/tiny-guard-2m-en-response-refusal-binary-polyguard

Content controls: not assessed.

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

Download availability is being checked.

Hashes recorded. Date not recorded.

FileGrößeSHA-256QuelleHerunterladen
Weights
model.safetensors7.91 MB
5ae05242…2e4bb2fe5ae052422f86949ca2cc9082c025812a7b948144b841c9f1ccf4e2672e4bb2fe
Download availability is being checked.File metadata
Tokenizer & config
config.json97 bytes
1741538a…3420110a1741538ae17122bc7a96784232618eddba4d278eb13dc8f890ebb8f63420110a
Download availability is being checked.File metadata
modules.json278 bytes
a68dcbed…244e45b2a68dcbed0429dcdd5bfdca92b0b03cc30d09122c0a3fcf4758787d4b244e45b2
Download availability is being checked.File metadata
pipeline.skops1.03 MB
7dbf9269…3f66ac1a7dbf92695bd32168c1ecfb33503d1dadce6c0cb52c08db4a68a4085c3f66ac1a
Download availability is being checked.File metadata
tokenizer.json446.3 KB
273ca9e2…9ba3bf62273ca9e28ec6990aea6206b0364443754d87e87a5dd28e94026ea9999ba3bf62
Download availability is being checked.File metadata
Docs
.gitattributes1.57 KB—Download availability is being checked.File metadata
README.md18.6 KB—Download availability is being checked.File metadata

Einen Download prüfen

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.