Lexicon Garden

at.happyproto.plugin.profile

A HappyView plugin package, in its publisher's repo. The record key is the package slug, so the slug is immutable: changing it means a different package.

Repository @happyproto.at did:plc:mo7vq4jbioxwafy5zkcc3eux namespace authority
Details · record, key any
Kindrecord
Record keyany
Authorityplugin.happyproto.at
Indexed
Compare Edit in builder → Fork →

Record

record · key any

Properties

authors

requiredarray
  • minLength: 1
itemsref
Reference

description

string

One line, 140 graphemes or fewer recommended.

  • maxLength: 3000
  • maxGraphemes: 300

keywords

array

Five or fewer recommended.

  • maxLength: 20
itemsstring
  • maxLength: 320
  • maxGraphemes: 32

lastUpdated

string · datetime

license

requiredstring

An SPDX expression, or the literal 'proprietary'.

  • maxLength: 256

name

string

Display name. The slug is used when absent.

  • maxLength: 640
  • maxGraphemes: 64

sections

ref
Reference

security

requiredarray

Where to report a vulnerability. At least one, because a plugin runs as native code in an operator's process.

  • minLength: 1
itemsref
Reference

type

requiredstring

Names the ecosystem. A client that does not understand the value refuses the package rather than guessing.

  • const: "happyview-plugin"

#author

object

Properties

email

string
  • maxLength: 320

name

requiredstring
  • maxLength: 640
  • maxGraphemes: 64

url

string · uri

#contact

object

A security contact. Either field satisfies it, but an entry with neither says nothing.

Properties

email

string
  • maxLength: 320

url

string · uri

#sections

object

Long-form CommonMark, rendered as untrusted input with raw HTML stripped.

Properties

changelog

string
  • maxLength: 20000
  • maxGraphemes: 2000

description

string
  • maxLength: 20000
  • maxGraphemes: 2000

installation

string
  • maxLength: 20000
  • maxGraphemes: 2000

security

string
  • maxLength: 20000
  • maxGraphemes: 2000

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • com.emdashcms.experimental.package.profile

    record not from the namespace authority

    Plugin package profile record. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.package.profile.

  • at.happyproto.registry.project

    record

    The HappyView facts about a software.release.project that make it a plugin. The record key is the project's name, and the record lives in the same repo as the project. The registry indexes a project's releases only while this record exists and is valid.

  • at.happyproto.plugin.v1

    object

    A HappyView plugin, as one entry in a software.release.manifest's `artifacts`. It carries the module and its manifest.json as blobs, so they are verified by their CIDs, and the manifest's facts in the signed record, so a consent screen renders without downloading the module. Those facts are not trusted: the loader checks them against the module itself and refuses a plugin that misstates what it does. The registry refuses a manifest whose artifact breaks a rule stated here, including the ones a l

  • com.emdashcms.experimental.publisher.profile

    record not from the namespace authority

    Identity-level metadata for a plugin publisher. One record per publisher DID, located at rkey `self`. Optional: a DID may publish packages without ever publishing a publisher.profile, in which case clients fall back to the publisher's handle and per-package metadata for display. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.publisher.profile.

  • at.happyproto.plugin.release

    record

    One version of a package. The record key is '<slug>:<version>'. A release at a given version is never modified: a registry that later sees a different CID at this key keeps the first and flags the conflict.