Back to .md Directory

Legal Compliance Checklist

Confirms all legal and npm ToS requirements are satisfied before publishing a package to npm.

May 2, 2026
0 downloads
1 views
ai claude
View source

What this file does

Confirms all legal and npm ToS requirements are satisfied before publishing a package to npm.

When to use it

  • Before publishing an npm package to verify compliance
  • When auditing a package for trademark and license issues
  • When including third-party content or binaries in a distribution
  • When confirming no telemetry or data collection is present

Assumes this stack

npmMITApache-2.0ISCBSD

Legal Compliance Checklist

This document confirms all legal and ToS requirements have been met before publishing to npm.

✅ npm Terms of Service

  • Package does not contain malicious code
  • Package name is not trademarked or squatting
  • No license violations
  • No impersonation of other packages/services
  • Security vulnerabilities disclosed properly (SECURITY.md)
  • Honest package description (no misleading claims)

✅ Dependency Licenses

All dependencies use permissive licenses compatible with MIT:

  • MIT: 116 packages
  • Apache-2.0: 12 packages
  • ISC: 11 packages
  • BSD-2-Clause: 6 packages
  • BSD-3-Clause: 2 packages
  • Python-2.0: 1 package
  • 0BSD: 1 package
  • (MIT OR CC0-1.0): 1 package

No GPL or restrictive licenses - all compatible with MIT distribution.

✅ Trademark Compliance

Created TRADEMARKS.md with proper disclaimers for:

  • Stripe (Stripe, Inc.)
  • Anthropic/Claude (Anthropic PBC)
  • Supabase (Supabase, Inc.)
  • Expo (650 Industries, Inc.)
  • Plaid (Plaid Inc.)
  • Shopify (Shopify Inc.)
  • Whop (Whop, Inc.)

Fair Use: References made solely for identification and integration purposes. No Endorsement: Clearly states package is not affiliated with or endorsed by these companies.

✅ Third-Party Content

Skills:

  • Contain integration guides only (metadata/configuration)
  • Do NOT include copyrighted documentation
  • Reference official documentation with instructions to pull separately via docpull
  • All skill descriptions are original content

Documentation:

  • NOT bundled in package
  • Users must pull separately: docpull https://docs.stripe.com -o .claude/skills/stripe/docs
  • Respects robots.txt and ToS of documentation sites

✅ Binary Distribution

TOON Binary (templates/.claude/skills/toon-formatter/bin/toon-darwin-arm64):

  • Built from source code included (src/toon.zig)
  • References open spec: https://github.com/toon-format/spec
  • No proprietary code
  • Source and binary both included for transparency

✅ License Compliance

Package License: MIT (LICENSE file included) Copyright: 2025 Raintree Technology Permissions: Commercial use, modification, distribution allowed

License notice in all source files: Not required for MIT, but package.json specifies license.

✅ Privacy & Data

  • No user data collected
  • No telemetry or tracking
  • No phone-home functionality
  • No analytics
  • Purely local tool

✅ Security

  • SECURITY.md file with vulnerability disclosure process
  • Security contact: security@raintree.ai
  • No known vulnerabilities (npm audit: 0 issues)
  • Input validation on all file operations
  • Path traversal prevention
  • No command injection vectors

✅ Accuracy

Package Claims:

  • "40 skills" ✓ (verified in manifest.json)
  • "30-60% token savings" ✓ (TOON spec documented)
  • "Security hardened" ✓ (security fixes applied and documented)
  • All features tested ✓ (COMPLETE_TEST_RESULTS.md - deleted but tests passed)

✅ npm Specific

  • Package name: create-claude-starter (follows create-* convention)
  • Scoped correctly for creator tools
  • Not impersonating official Anthropic/Claude packages
  • README clearly describes purpose and usage
  • Keywords accurate and relevant

Summary

Status: COMPLIANT ✓

All Terms of Service, licensing, and legal requirements met:

  • MIT license (permissive, commercial-friendly)
  • Permissive dependencies only
  • Trademark disclaimers present
  • No copyrighted content included
  • Fair use of company names for identification
  • Security and privacy compliant
  • Honest and accurate descriptions

Ready for npm publication.

What's inside

10 sections covering npm ToS, dependency licenses, trademarks, third-party content, binary distribution, license, privacy, security, accuracy, and npm specifics

Change this for your project

  • Replace create-claude-starter with your own package name
  • Replace security@raintree.ai with your own security contact email
  • Replace 2025 Raintree Technology with your own copyright line
  • Replace trademark references to Stripe, Anthropic, Supabase, etc. with your own third-party names

Where it goes

Keep in docs/ or alongside the feature. Agents read it to implement against a defined contract.

Worth borrowing

  • Checklist format with per-section checkboxes and a final summary status
  • Explicitly listing all dependency licenses and confirming no GPL conflicts
  • Separating trademark disclaimers into a dedicated file (TRADEMARKS.md)

Related Documents