# Upstream origin and triage

- Original package: `update-notifier@6.0.2`
- Repository: https://github.com/yeoman/update-notifier
- Source commit: https://github.com/yeoman/update-notifier/commit/3b6b9b18428aa3848960f02df53cb571a7620a51
- Source directory: `.`
- npm tarball: https://registry.npmjs.org/update-notifier/-/update-notifier-6.0.2.tgz
- SHA512 integrity: `sha512-EDxhTEVPZZRLWYcJ4ZXjGFN0oP7qYvbXWzEgRm/Yql4dHX5wDbvh89YHP6PK1lzZJYrMtXUuZZz8XGK+U6U1og==`
- npm last-release age selects maintenance scope; it does not imply no ongoing source development.

## Reviewed issues

Primary-source snapshot: `2026-09-29T00:22:23.297567+00:00`. Most recently updated 100 open and 30 closed issue/PR entries; PRs removed. This is triage evidence, not a claim of exhaustive review.

Maintenance adoption with preserved runtime payload. No runtime defect correction is claimed. Reports remain visible for subsequent targeted reproduction.

- [100: Private npm registry](https://github.com/sindresorhus/update-notifier/issues/100)
- [240: TypeScript types](https://github.com/sindresorhus/update-notifier/issues/240)
- [210: Run in child process instead of lazy loading every dependency](https://github.com/sindresorhus/update-notifier/issues/210)
- [213: Notify Option to show Changelog in default message.](https://github.com/sindresorhus/update-notifier/issues/213)
- [220: Fix tests on Linux](https://github.com/sindresorhus/update-notifier/issues/220)
- [172: Default `pkg` to the current package](https://github.com/sindresorhus/update-notifier/issues/172)
- [180: Better adhere to XDG specification](https://github.com/sindresorhus/update-notifier/issues/180)
- [209: Notification is only displayed at most once per interval](https://github.com/sindresorhus/update-notifier/issues/209)
- [201: Update notifier not working with public npm package](https://github.com/sindresorhus/update-notifier/issues/201)
- [196: Conflicts happen if two projects use the same local package](https://github.com/sindresorhus/update-notifier/issues/196)
- [170: Log using process.stderr.write instead of console.error since this isn't an error](https://github.com/sindresorhus/update-notifier/issues/170)
- [169: check.js: Please don't run checkNpm when disabled is true](https://github.com/sindresorhus/update-notifier/issues/169)
- [129: Allow simply showing notification for manual checks (with callback)](https://github.com/sindresorhus/update-notifier/issues/129)
- [139: Should isGlobal work with npm link?](https://github.com/sindresorhus/update-notifier/issues/139)
- [140: update-notifier creates lots of troubles](https://github.com/sindresorhus/update-notifier/issues/140)
- [137: EACCES or EPERM improvement](https://github.com/sindresorhus/update-notifier/issues/137)
- [120: Make it work for Semantically Release packages](https://github.com/sindresorhus/update-notifier/issues/120)
- [56: Package deprecation notice](https://github.com/sindresorhus/update-notifier/issues/56)
- [112: Bad advice when using npx](https://github.com/sindresorhus/update-notifier/issues/112)

The structured snapshot in `.stackline/issue-triage.json` also records recently closed reports. Issues for unrelated packages in shared monorepositories were qualified as outside this fork’s runtime scope. No maintainer was contacted.