Publishing and moderation rules
Requirements for open-source Pulse modules, review checks, complaints, withdrawals and appeals.
Source and license
Publish module source in a public GitHub repository with an explicit license allowing use, study, modification and redistribution. A public repository alone is not a license. Identify dependency licenses and preserve required attribution notices.
Package and permissions
Releases must follow the published Pulse protocol and include an installation JSON, version, supported platforms and required permissions. Distributed builds must correspond to the published source. Explain access to Docker sockets, files, networks and elevated privileges; disclose external connections and data transfers.
Discovery and validation
Marketplace discovers repositories using the pulse-module topic and protocol marker. Passing format, platform and digest validation does not automatically publish a module: the revision enters moderation. The current implementation supports personally owned GitHub repositories; organization publishing is not yet supported.
Moderation decisions
The project operator moderates revisions and may approve, reject or withdraw them with a reason. A moderator-role user cannot approve their own module; an administrator can do so with an audit record. Approval is not an independent audit, a guarantee of vulnerability-free code or a promise of compatibility with every system.
Disallowed content
Hidden data transfers, credential theft, backdoors, malicious behavior, package/owner impersonation, undisclosed mining, rights or license violations, false verification claims and catalog restriction bypasses are prohibited. Legitimate administration and security tools are assessed by their stated purpose, transparency and behavior.
Versions and account deletion
Approved packages are retained as SHA-256 snapshots. Deleting an account does not automatically delete published versions: they may remain available under their licenses with required attribution. This does not authorize indefinite retention of unnecessary profile data. Personal data deletion requests and rights complaints are considered separately.
Complaints and appeals
Email support@hubba-cloud.ru, or heyhubbabubbapr@gmail.com if delivery fails. Identify the module, version, decision or violation, evidence and requested action. Decisions can be appealed with new facts or an explanation of an error. The same operator handles appeals; there is no independent appeals panel. There is no fixed response SLA, without affecting legally required deadlines.
Withdrawal and new releases
A version may be hidden or withdrawn for security threats, tampering or rights violations. Previously downloaded copies are not automatically removed or disabled. Changed packages require a new review; earlier approval does not cover new bytes.