malicious url detection EU AI Act Compliance Profile
kmack
Your risk depends on how you use malicious url detection
| Usage Context | Risk Level | Obligations |
|---|---|---|
| Internal coding tool | MINIMAL | 3 obligations (~12h) |
| Customer support bot | LIMITED | 7 obligations (~32h) |
| HR screening / hiring | HIGH | 19 obligations (~120h) |
| Credit decisions | HIGH | 19 obligations (~120h) |
| Medical triage | HIGH | 19 obligations (~120h) |
Why this tool is classified as LIMITED RISK
malicious url detection is a text classification model by kmack. Built with transformers. Supports en. Licensed under apache-2.0. 39.7K downloads on HuggingFace.
Applicable Articles
Who does what
kmack (provider)Their job
- Provider obligations being compiled
You (deployer)Your job
- •AI Literacy (Art. 4) (Art. 4)
- •AI Disclosure (Art. 50) (Art. 50)
Risk Assessment Reasoning
This model is classified as Limited Risk under the EU AI Act. Deployers must comply with transparency obligations (Art. 50), ensuring users are informed they are interacting with an AI system. AI literacy training (Art. 4) is also required. If used for profiling or automated decision-making affecting individuals, additional GDPR Art. 22 obligations apply.
Similar Models
Frequently Asked Questions
What is malicious url detection's EU AI Act risk classification?
+
malicious url detection is classified as LIMITED RISK under the EU AI Act.
What are my obligations if I deploy malicious url detection?
+
As a malicious url detection deployer, you have 2 base obligations (~12 hours estimated effort). Key articles: Art. 4, Art. 50.
What is malicious url detection?
+
malicious url detection is a Text Classification model by kmack. It has 39.7K downloads on HuggingFace. Licensed under apache-2.0.
What are the EU AI Act deadlines for malicious url detection?
+
Already passed: AI Literacy (Art. 4) — 2025-02-02. Already passed: AI Disclosure (Art. 50) — 2025-08-02.
Check malicious url detection compliance in your codebase
One command to scan. Open-source CLI.