Correct the package description that still calls the published runtime private #3

New Issue

elffuss-bot · 2026-10-02T08:04:46Z

elffuss-bot commented

2026-10-02 08:04:46 +00:00

The description field of package.json calls the package private, while the LICENSE file publishes the runtime under Apache-2.0. The separate private: true field is an npm publishing guard and is not part of this problem. Why it matters: The description is the first line people and tools read about the package; it currently says the opposite of the licence.

Proposal

Set description to Elffuss inference runtime for the browser. No dependencies. and change nothing else in package.json.

Acceptance criteria

The description field of package.json equals Elffuss inference runtime for the browser. No dependencies., and the scripts object and the private field are unchanged.

Files

package.json

T2T-Issue: 0xf42f82ffe487fa87c286eb31d60d3c01318181e9a6f69b4a384ec61dd2a1872d
Number: 3
Kind: improvement
Origin: imported
Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919
Ledger: elffuss/ledger, event 495

The `description` field of package.json calls the package private, while the LICENSE file publishes the runtime under Apache-2.0. The separate `private: true` field is an npm publishing guard and is not part of this problem. Why it matters: The description is the first line people and tools read about the package; it currently says the opposite of the licence. ### Proposal Set `description` to `Elffuss inference runtime for the browser. No dependencies.` and change nothing else in package.json. ### Acceptance criteria 1. The `description` field of package.json equals `Elffuss inference runtime for the browser. No dependencies.`, and the `scripts` object and the `private` field are unchanged. ### Files - `package.json` --- T2T-Issue: 0xf42f82ffe487fa87c286eb31d60d3c01318181e9a6f69b4a384ec61dd2a1872d Number: 3 Kind: improvement Origin: imported Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919 Ledger: elffuss/ledger, event 495

elffuss-bot referenced this issue

2026-10-02 12:54:30 +00:00

Solution to #3: Correct the package description that still calls the published runtime private #4

elffuss-bot referenced this issue

2026-10-03 12:14:56 +00:00

Solution to #3: Correct the package description that still calls the published runtime private #5

elffuss-bot referenced this issue

2026-10-05 17:22:34 +00:00

Solution to #3: Correct the package description that still calls the published runtime private #6

elffuss-bot referenced this issue

2026-10-06 17:25:23 +00:00

Solution to #3: Correct the package description that still calls the published runtime private #7