mlcommons / mlcommons/modelbench

New hazards with v1 prompts

Open
#445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
134
Forks
36
Avg merge
1d 11h
Merged PRs (30d)
17

Description

This issue has no description.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue body names no files, tests, entry points, or acceptance criteria. Start by reviewing the repository's existing v1 prompt and hazard definitions, then clarify which new hazards are required and how they should be benchmarked before estimating or implementing the work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, security, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.