Skip to content
Contents

compliance changelog

Every compliance release, newest first.

Versions

  1. 0.1.1

    4 fixed

    Fixed

    • evaluateBeatmapset reads a missing moreInformation (hand-built facts, or a row without the column) as no content notice, like factsFromOsuBeatmapset does. Before, it returned disallowed/dmca for every set.
    • The data check at import rejects an empty artist name (artists/restricted.json, labels/MEGAREX.json) or track name (labels/MEGAREX.json). One would have matched every title. The shipped data passes.
    • The data error names the file as data/<file>, which exists in the installed package, instead of src/data/<file>.
    • The README's Limits say rule 6 is a substring match and name the short track names that flag unrelated titles.

  2. 0.1.0

    5 added

    Added

    • evaluateBeatmapset: the osu! mappool content rules, ported from hburn7/omc-api, with verdicts ok, potential or disallowed and a reason.
    • factsFromOsuBeatmapset builds the input from an osu! API v2 beatmapset.
    • verdictText, REASON_TEXT and the other text constants for showing verdicts.
    • isLeaderboardStatus, COMPLIANCE_STATUSES, COMPLIANCE_REASONS, UPSTREAM and RULE_LINKS.
    • Artist, override, source and label data vendored from omc-api at bb356b3 (2026-06-28), with hashes pinned in docs/vendored-data.md.