@readystack/spdx-license-field-lint

Name: @readystack/spdx-license-field-lint
Author: io.github.jmshinhwa

MCPcommunity

v0.1.4io.github.jmshinhwaSEE LICENSE IN LICENSE.txtUpdated todaynpm GitHub

Reads the licence field in the open manifest and names every deprecated SPDX id, invalid string, PEP 639 leftover and copyleft obligation - with the exact replacement text.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

todayLast update

Package

Authorio.github.jmshinhwa

LicenseSEE LICENSE IN LICENSE.txt

Version0.1.4

Sourcenpm+mcp-registry

npm@readystack/spdx-license-field-lint

GitHubjmshinhwa/readystack-themes

SBOMCycloneDX 1.6 ↓

Trust Status

10/100Untrusted

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

—Static analysis · clean+0/20

→ Not yet scanned — package must be on npm

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scanNot runHow well does this scan work?

EvalsNone

IndexedSep 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Not scanned yet

Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.

About

Reads the licence field in the open manifest and names every deprecated SPDX id, invalid string, PEP 639 leftover and copyleft obligation - with the exact replacement text.

Keywords

spdxlicensepep-639sbomcompliance

Alternatives

Comparing tool surfaces…

@readystack/spdx-license-field-lint

Tools

No dependency coverage