Repository navigation
chore: add package metadata and MIT license - #154
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The package declares an MIT license but has no LICENSE file. Its npm metadata lacks repository and issue tracker links.
Changes
lint-md/lint-mdwithout edits.The LICENSE keeps
Copyright (c) 2021 hustccfrom the main project. Maintainers can confirm this attribution for parser.Validation
pnpm run buildpassed. API reports did not change.pnpm run test:packagepassed.pnpm pack --dry-runlisted LICENSE, README.md, package.json, and all dist files.pnpm run test:builtpassed. It ran 2024 existing tests and 10 source tests.git diff --checkpassed.No runtime code or dependencies changed. No sensitive data was added or redacted.