Contribute to DevCannabis

We're building reliable, ongoing, transparent cannabis data from creative, consistent, and curious contributors. Find your role, submit source-backed corrections, or request approved contributor/source access.

Start Here

Every path is manually reviewed. Source, correction, API, reviewer, developer, and partner requests are approval-based.

Submit a source Send an official public government/regulatory source URL for review. Report a correction Flag a data issue with evidence, source URL, and what should change. Request API access Request review for fair-use API/export access; approved requests receive a scoped API key. Apply to be a moderator/reviewer Help triage corrections, verify evidence, and review provenance. Request developer/source access Approved contributors may work on adapters, tests, dashboards, API, or data quality. Partner/commercial inquiry Review access terms before requesting commercial, bulk, model-training, or republication rights.

Public dashboards are free. API/export access follows request → approval → scoped API key or contributor login, with fair-use rate limits and usage logging. Free non-commercial fair-use access requires attribution; bulk export, resale, republication, model training, competing products, and commercial use require written permission. See the Access Policy.

Contributor roles, explained

Contributions are controlled and source-backed. Choose the path that matches what you can help with.

Developer Contributor / State Lead

Approved access

Request approved source access to build adapters, pipelines, tests, dashboards, or API improvements. State Leads take ongoing responsibility for one jurisdiction.

Build and maintain approved scraper/pipeline work
Ensure weekly data updates
Submit PRs under project contribution terms
Document state-specific quirks

Data Contributor

Public-source corrections

Submit official source links, provenance notes, data-quality reports, and source-backed corrections. No broad source access is required for this path.

Submit official regulator source URLs
Report data discrepancies with evidence
Add provenance and source notes
Help verify edge cases and aliases

Moderator / Reviewer

Trusted review role

Help review source evidence, validate corrections, triage issues, and keep contributions aligned with project integrity and licensing terms.

Review source-backed submissions
Check provenance and uncertainty labels
Triage bugs and corrections
Escalate quality or license concerns

Partner / researcher path: public outputs may be used for non-commercial public-interest work with attribution. Request approval for deeper collaboration, commercial use, hosted-service rights, or bulk/API access beyond normal limits.

States & territories

Follow states to get updates, submit official sources, or apply for approved developer/reviewer roles. Seeking Lead means we need an approved maintainer for that jurisdiction.

Loading states...

Request a new state

Know a state with accessible public cannabis data? Request it here with a verified public government/regulatory source. This submits source/correction information; developer/source access is reviewed separately. Review status follows: submitted → needs_source → under_review → approved/rejected → published.

State/Territory Code *

State/Territory Name *

Regulatory Agency *

Agency Website *

Official Public Government/Regulatory Data URL *

Must be an official government or regulatory source. Private, news, or advocacy links are kept only as non-canonical references.

Data Format *

Why should we add this state? *

I'm willing to be the Lead Developer for this state

This is a US territory (not a state)

How it works

Sign In

Use GitHub to create your contributor profile

Choose Your Path

Submit sources/corrections, apply for developer access, or request reviewer/moderator status

Contribute

Work through approved roles under project contribution and licensing terms

Grow

Learn, collaborate, and build your public data portfolio

Submit a Request

One lightweight intake for sources, corrections, API access, reviewer/moderator applications, developer/source access, and partner inquiries.

Protected access is never automatic — every request is manually reviewed and approved before any key is issued.

What do you need? *

Manual review/approval is required for API, moderator/reviewer, developer/source, partner, commercial, bulk, export, and model-training access.

Your details

Name

GitHub username

Organization

State / jurisdiction

Source URL

Canonical sources must be verified public government or regulatory organizations. Other links are kept as non-canonical references.

Intended use *

Details *

I agree to the Access Policy and contribution terms. I understand protected, API/export, bulk, commercial, republication, and model-training use require written approval.