Skip to main content

​
Overview

A CI/CD License enables automated builds in continuous integration and deployment pipelines. Unlike Individual or Team Licenses which require interactive GitHub authentication, the CI/CD License uses a token that can be stored as an environment variable. Each subscription includes one CI/CD License that can be used across all your pipelines.
The CI/CD License is designed for automation. Use it in GitHub Actions, CircleCI, Bitrise, Azure Pipelines, or any other CI/CD system.

​
How It Works

  1. Create your CI/CD License from your dashboard
  2. Store the token as UNIWIND_AUTH_TOKEN secret in your CI/CD platform
  3. Run install - the postinstall script automatically authenticates and downloads
  4. Build your app with Uniwind Pro included

​
Download Limits

MetricLimit
Monthly downloads1,000
Reset period1st of each month
CI/CD pipelines typically run more frequently than manual installs. The 1,000 download limit accommodates most team workflows with room to spare.
Need higher limits? Contact [email protected] to discuss extended quotas for your pipelines.

​
Creating Your CI/CD License

  1. Navigate to your dashboard
  2. Go to Licenses section
  3. Click Add License
  4. Select CI/CD license type
  5. Click Create
You’ll receive a license UUID that serves as your CI/CD token. Use this single token across all your pipelines.
Treat your CI/CD token like a password. Never commit it to version control. Always use secret management.

​
Pipeline Configuration

The uniwind-pro package automatically detects CI/CD environments. Simply set the UNIWIND_AUTH_TOKEN environment variable with your CI/CD license UUID, and the postinstall script will handle authentication automatically. 
UNIWIND_AUTH_TOKEN=your-license-uuid
When UNIWIND_AUTH_TOKEN is set, the postinstall script automatically downloads Uniwind Pro during npm install (or your package manager’s install command).

​
Example: GitHub Actions

.github/workflows/build.yml
name: Build App

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Node
        uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install dependencies
        run: npm install
        env:
          UNIWIND_AUTH_TOKEN: ${{ secrets.UNIWIND_AUTH_TOKEN }}

      - name: Build
        run: npm run build
Add UNIWIND_AUTH_TOKEN to your repository secrets in Settings > Secrets and variables > Actions.
Cache your node_modules to reduce CI/CD download count. Downloads only occur when uniwind-pro is not already in node_modules.

​
Security Best Practices

Use secret management

Never hardcode the token. Use your CI platform’s secret management.

Rotate periodically

Regenerate your token from the dashboard if you suspect it’s compromised.

Use caching

Cache the package to minimize downloads and reduce exposure of your token.

Monitor usage

Review CI/CD license usage in your dashboard for anomalies.

​
Troubleshooting

The license token is invalid or not set. Check that:
  • UNIWIND_AUTH_TOKEN environment variable is set correctly
  • The token is correctly copied (no extra spaces)
  • The license hasn’t been revoked
  • The subscription is active
You’ve exceeded the 1,000 monthly download limit. Options:
  • Cache node_modules to reduce downloads
  • Wait for monthly reset
  • Contact support for limit increase
Some CI environments disable postinstall scripts. Ensure your package manager allows them, or see the Installation guide for whitelisting instructions.

Individual License

Personal license for development

Team License

Shared license for team projects