ransom object

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
security

Research direction

The issue names no files, tests, entry points, or requirements beyond “ransom object.” Start by reviewing the repository’s existing object definitions and similar security-related objects, then clarify the expected fields and relationships. Done should mean an agreed ransom object definition is added and validated consistently with the project’s existing definitions.

Written by the indexing model from the issue text.

Description

enhancement

ransom object

Dominant language
Python
Stars
110
Forks
139
Avg merge
12h 28m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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.

More from MISP/misp-objects

All issues in MISP/misp-objects

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.