Skip to content

Declare and ship an open-source license #126

Description

@itsjling

Problem

The npm package does not declare a license. The npm registry omits license, deps.dev reports no licenses, npm.io shows Licence —, and GitHub's community profile reports no license.

This is the clearest actionable fault in the current package-health data. It leaves users unsure whether they may use, copy, or change the package.

Decision needed

The maintainer must choose the license. Do not infer one from dependencies or other projects. Record the chosen SPDX identifier.

Scope

  • Add the full license text in a root LICENSE file.
  • Add the matching SPDX identifier to package.json.
  • Extend the package-manifest checks so a release cannot omit or mismatch the license.
  • Confirm the packed tarball contains the license.
  • Note the license in release notes if the choice changes users' rights.

Acceptance checks

  • npm pack --dry-run includes LICENSE.
  • The packed package.json has the chosen SPDX identifier.
  • corepack pnpm run package:verify passes.
  • corepack pnpm run lint and corepack pnpm test pass.
  • After release, the npm registry and deps.dev show the chosen license.

Evidence

  • npm package metadata for 0.12.1 has no license field.
  • deps.dev returns licenses: [] for 0.12.1.
  • GitHub's community profile is 28% and reports license: null.
  • npm.io shows Licence —.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestready-for-agentFully specified and ready for an agent

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions