[email protected] is published without a `license` field

Open Beginner friendly
#816 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
nodejs, typescript
Domain
release

Research direction

Open packages/plugin-form/package.json and compare it with a sibling such as packages/plugin-annotation/package.json, which already declares "license": "MIT". Add the same field alongside the other top-level metadata keys, keeping the existing key order and formatting of the repo. Done means plugin-form's package.json declares MIT like its 26 siblings; a maintainer republish of the 2.15.x line is a separate step the issue also mentions.

Written by the indexing model from the issue text.

Description

Summary

@embedpdf/[email protected] is published to npm without a license field in its package.json. It is the only package in the 2.15.0 line we depend on that has this gap — all 26 of its siblings declare "license": "MIT".

Reproduction
$ npm view @embedpdf/[email protected] license
                       # empty, exit 0

$ npm view @embedpdf/[email protected] license
MIT

Checked across the 27 @embedpdf/* packages at 2.15.0 (pdfium, engines, core, models, utils and 22 plugin-*): every one returns MIT except plugin-form, which returns nothing.

Why it matters

Automated licence scanners read package.json, not the tarball. With the field missing, plugin-form is reported as "unknown" / "n/a" and shows up as an unresolved item in compliance review, even though the actual licence is not in doubt.

The intent is clearly MIT: the published tarball does contain a LICENSE file, and it is byte-identical (md5 d93898f5290c053cdf184d7f57c8074f) to the one shipped in @embedpdf/[email protected], @embedpdf/[email protected] and 21 other packages at the same version — "MIT License, Copyright (c) 2025 CloudPDF". So this looks like a packaging omission rather than a deliberate difference.

This is the same class of problem as #168 (which added the field across the repo for the 1.2.x line, merged 2025-09-22); the 2.15.0 publish of plugin-form appears to have regressed or been missed.

Request

Add "license": "MIT" to packages/plugin-form/package.json so the declared metadata matches the shipped LICENSE file. A republish of the 2.15.x line would be ideal, but having it correct going forward is the main thing.

Happy to open a PR if that is easier.

Dominant language
TypeScript
Stars
4.5k
Forks
317
Avg merge
10h 16m
Merged PRs (30d)
174

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from embedpdf/embed-pdf-viewer

All issues in embedpdf/embed-pdf-viewer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.