Chahuadev Docs

Overview

Chahuadev allows the public to access selected Electron + Node.js app packages through official npm channels for testing. This page defines what testers may do, what they may not do, and how that public access should be interpreted.

Public npm availability supports internal evaluation, compatibility review, security review, QA validation, and limited hands-on testing. It does not create a public right to redistribute, mirror, sell, host, embed, or commercially deploy Chahuadev applications.

Allowed testing actions

Action Status Scope
Install from official npm package pages Allowed For internal evaluation and testing only.
Run the app in internal QA or compatibility workflows Allowed Only where the use remains non-commercial and internal.
Inspect app behavior, UI, workflow, and runtime characteristics Allowed For review, testing, and evaluation.
Perform internal security review Allowed So long as the activity stays within the public license boundary.

Restricted and prohibited actions

Action Status Reason
Production deployment or customer-facing use Not granted Commercial and operational rights are reserved.
Redistribution, repackaging, mirroring, or third-party hosting Prohibited Public testing access does not create distribution rights.
Embedding the apps into another product or service Prohibited No integration or derivative commercialization right is granted.
Client work, paid consulting, managed service, OEM, or resale use Prohibited These activities require a separate written commercial agreement.

Distribution interpretation standard

Where Chahuadev publishes a public app package, the default interpretation is:

  • The package is an Electron + Node.js app build made available for testing.
  • The package is delivered through an official Chahuadev npm channel.
  • The package is not a grant of open-source rights.
  • The package is not a grant of distribution, resale, or production rights.
  • The package remains subject to the source-available proprietary license and legal controls.

Document priority

If there is any question about scope, the controlling order is simple: the license governs first, this testing policy explains public distribution intent second, and the legal controls page documents enforcement posture and channel controls.

Commercial or broader usage

If you need production rights, customer deployment rights, redistribution rights, OEM rights, or any commercial permission, contact Chahuadev directly at chahuadev@gmail.com. Public npm visibility does not replace a written agreement.