Broken author url
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- tooling
Research direction
The issue points to package.json and tsdown.config.ts. Start by checking the author URL in package.json and see how it's used in tsdown.config.ts to generate the banner. Remove or update the URL in package.json, then verify the change by building the project and checking the output JavaScript files for the presence of 'http://kiro.me'.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues
Description of the bug
In package.json, the "author"->"url" property contains "http://kiro.me", which is inaccessible.
This URL finds its way to the script's banner due to tsdown.config.ts.
Some consumers with a strong security posture are concerned that the inactive domain could be acquired and used maliciously. Users or security tools inspecting the JavaScript file could be directed to an untrusted site.
Would you able to revive the broken website? Or remove the URL from the script's banner?
The Fuse.js version where this bug is happening.
6.6.2
Is this a regression?
- This is a regression bug
Which version did this behavior use to work in?
None
Steps To Reproduce
Open any JavaScript file in the distributed package, and search for "http://kiro.me".
Expected behavior
The "http://kiro.me" website works, or is excluded from the script banner.
Screenshots
No response
Additional context
No response
- Dominant language
- JavaScript
- Stars
- 20.5k
- Forks
- 828
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from krisk/Fuse
-
Extended search drops any query term that contains a line breakPossibly taken @goranai claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:mcp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day