feat: add license and metadata to package.json #19
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
- Add MIT license field - Add repository, homepage, and bugs URLs - Add description for the package - Add relevant keywords (anthropic, auth, opencode, openauth, plugin) - Add original author attribution (anomalyco) Fixes anomalyco#5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR enhances the
package.jsonwith essential metadata fields that were previously missing. These additions improve package discoverability, provide proper licensing information, and establish clear links to the project repository.Changes
Benefits
✅ NPM Registry Compliance: Package metadata is now properly configured for npm, making the package easier to discover and use as a dependency
✅ Better Documentation: Users can easily find the source code, report issues, and understand the package purpose
✅ Professional Standards: Follows npm best practices for package.json configuration
✅ License Clarity: Makes the MIT license explicit in package metadata, improving compliance and usage transparency
Fixes
Closes #5
Testing
No testing required - this is a metadata-only change. Users can verify the changes by checking the package metadata on npm or installing the package locally.
Done with OpenCode | Share Link