Broken author url

Open Beginner friendly
#851 0 comments 0 reactions 0 assignees View on GitHub

@Doomguy-BFG9000 is already working on this.

Since Nov 7, 2026.

  • #859 by @Doomguy-BFG9000 — open

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

bug
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from krisk/Fuse

All issues in krisk/Fuse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.