Submission (Certified Plugins)

This is the flow for publishing a certified plugin on the marketplace.

STEP 1: Register as a developer

On the marketplace My Page, register a developer profile (display name, slug).

STEP 2: Claim a namespace

Claim the @scope part (the namespace) of your plugin ID. To submit @your-org/tasks, you must own @your-org.

STEP 3: Issue a publishing token (PAT)

On My Page, issue a Personal Access Token with plugin.* scopes. This token is exclusively for the developer portal and cannot be used for the regular API (the credentials are separated).

Scope	Use
plugin.publish	Create and submit applications
plugin.read.stats	View install statistics
plugin.manage	Manage profile and namespaces

STEP 4: Submit

The CLI handles build, validation, and submission all at once.

NIYASE_TOKEN=<your plugin.publish PAT> niyase-plugin publish
# ✓ built (sha256 …)
# ✓ manifest validation OK (@your-org/tasks)
# ✓ application submitted (state=SUBMITTED)

Internally, publish performs: build → validateManifest() → create application → upload bundle (sha256) → request review. Adding --dry-run stops after validation (it does not go to the network).

STEP 5: Review → publication

The application advances through a state machine:

DRAFT → SUBMITTED → IN_REVIEW → { CHANGES_REQUESTED | APPROVED | REJECTED }
APPROVED → PUBLISHED

niyase staff review the manifest and bundle, and approve → publish lists it on the marketplace. If changes are requested, it is sent back with comments, and you can fix and resubmit.

After publication

• Version updates are re-reviewed as new applications
• Check install counts and application status on the My Page dashboard
• Integrity: the distributed bundle is checked against the sha256 from upload time; if they do not match, it is not delivered