fix(repo): point package metadata at this project, not upstream - #18
Merged
Conversation
All twelve manifests — the root and eleven packages — still carried upstream's `homepage`, `bugs`, `repository` and `author`. Those fields are what npm renders on a package page, and what `npm bugs` and `npm repo` open. Publishing as-is would have shipped every package with a contact address that does not accept reports for this build, which is the exact failure this project was started over. homepage -> https://spotlight-rules.com bugs -> https://github.com/api-commons/spotlight-tools/issues repository -> https://github.com/api-commons/spotlight-tools.git author -> API Commons <apicommons@gmail.com> contributors -> The Spectral contributors `author` states who answers for this build today. Naming Stoplight there would say they maintain it, and they do not. The lineage is credited in `contributors`, in the README and in the LICENSE, where it is accurate. `license` verified as Apache-2.0 in all twelve. Package names are deliberately untouched — that decision is #8, and nothing here depends on it. Closes #12 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
kinlane
commented
Aug 3, 2026
kinlane
left a comment
kinlane
left a comment
Contributor
Author
There was a problem hiding this comment.
LGTM -- all updated to point to api commons.
This was referenced Aug 3, 2026
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
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.
Closes #12.
All twelve manifests — the root and eleven packages — still carried upstream's contact metadata. These are the fields npm renders on a package page, and the ones
npm bugsandnpm repoopen.homepagegithub.com/stoplightio/spectralhttps://spotlight-rules.combugsgithub.com/stoplightio/spectral/issuesgithub.com/api-commons/spotlight-tools/issuesrepositorygithub.com/stoplightio/spectral(.git)github.com/api-commons/spotlight-tools.gitauthorStoplight <support@stoplight.io>API Commons <info@apicommons.org>contributorsauthorstates who answers for this build today. Naming Stoplight there would say they maintain it, and they do not. The lineage is credited incontributors, and more fully in NOTICE, the README and the LICENSE.licenseverified asApache-2.0in all twelve, unchanged.What this deliberately does not do
Package names are untouched. They are still
@stoplight/spectral-*. Renaming them is #8 and nothing here depends on that decision — which is the point of splitting it out. This lands the half that is not blocked, so that whenever #8 is settled the only remaining change is the name itself.Files: root
package.jsonpluspackages/{cli,core,formats,formatters,functions,parsers,ref-resolver,ruleset-bundler,ruleset-migrator,rulesets,runtime}/package.json.