update-notifier
Update notifications for your CLI app
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the consuming package's package.json for version checking — core functionality of an update notifier, not arbitrary module loading. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (ulisesgascon, mshima, ruyadorno) are well-known Node.js core collaborators; addition is consistent with legitimate open-source governance transition. | ai | |
| provenance | publisher-changed | AI (provenance): Transfer from sboudrias to sindresorhus is legitimate; sindresorhus is the documented author and a highly trusted npm publisher. This is a stable, expected transition for this package. | ai | |
| phantom-deps | phantom-dep:import-lazy | AI (phantom-deps): import-lazy is a declared runtime dep used for lazy-loading; static import analysis misses its usage pattern. Stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): is-in-ci replaces is-ci/has-yarn/is-yarn-global as a consolidation; it is a sindresorhus package consistent with this ecosystem. Not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:semver-diff | AI (dependencies): semver-diff is a standard utility for comparing semver versions, core to update-notifier's functionality. | ai | |
| dependencies | unvetted-dep:has-yarn | AI (dependencies): has-yarn is a small utility to detect yarn usage, appropriate for update-notifier to suggest the correct install command. | ai | |
| dependencies | unvetted-dep:is-ci | AI (dependencies): is-ci is a well-known utility for detecting CI environments, appropriate for update-notifier's use case of suppressing notifications in CI. | ai | |
| dependencies | unvetted-dep:is-yarn-global | AI (dependencies): is-yarn-global detects yarn global installs, used by update-notifier to tailor upgrade instructions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): sindresorhus is the canonical maintainer; dormancy reflects infrequent but legitimate maintenance, not account takeover. Changes are consistent with modernization. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects migration of an established project to npm; co-maintainer mass-production signal does not apply to this well-known sindresorhus/yeoman package. | ai | |
| dependencies | unvetted-dep:pupa | AI (dependencies): pupa is a long-standing sindresorhus utility for string interpolation; stable, low-risk dependency for this package. | ai | |
| phantom-deps | phantom-dep:is-yarn-global | AI (phantom-deps): Lazily required via import-lazy; used to detect global yarn installs. | ai | |
| phantom-deps | phantom-dep:latest-version | AI (phantom-deps): Lazily required via import-lazy; core dep for fetching latest npm version. | ai | |
| phantom-deps | phantom-dep:has-yarn | AI (phantom-deps): Lazily required via import-lazy; used to detect yarn usage. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process.fork is used to spawn a background update-check process, which is the canonical implementation pattern for non-blocking update notifiers. | ai | |
| phantom-deps | phantom-dep:pupa | AI (phantom-deps): Package uses import-lazy for lazy requires; static analysis cannot detect the require calls. All deps are legitimately used. | ai | |
| phantom-deps | phantom-dep:boxen | AI (phantom-deps): Lazily required via import-lazy; legitimate dep for rendering the update notification box. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Lazily required via import-lazy; legitimate dep for terminal coloring. | ai | |
| phantom-deps | phantom-dep:is-ci | AI (phantom-deps): Lazily required via import-lazy; used to suppress notifications in CI environments. | ai | |
| phantom-deps | phantom-dep:is-npm | AI (phantom-deps): Lazily required via import-lazy; legitimate dep. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Lazily required via import-lazy; used for version comparison. | ai | |
| phantom-deps | phantom-dep:is-installed-globally | AI (phantom-deps): Lazily required via import-lazy; legitimate dep. | ai | |
| phantom-deps | phantom-dep:configstore | AI (phantom-deps): Lazily required via import-lazy; used to cache version check results. | ai | |
| phantom-deps | phantom-dep:semver-diff | AI (phantom-deps): Lazily required via import-lazy; used to compute version difference type. | ai | |
| phantom-deps | phantom-dep:xdg-basedir | AI (phantom-deps): Lazily required via import-lazy; legitimate dep. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): Detached background process is update-notifier's documented design for checking updates without blocking the main app. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Detached background process is update-notifier's documented design for checking updates without blocking the main app. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 7.3.1 | 10 / 6 | |
| 7.3.0 | 10 / 6 | |
| 7.2.0 | 12 / 6 | |
| 7.1.0 | 12 / 6 | |
| 7.0.0 | 12 / 6 | |
| 6.0.2 | 14 / 6 | |
| 6.0.1 | 14 / 6 | |
| 6.0.0 | 14 / 6 | |
| 5.1.0 | 14 / 6 | |
| 5.0.1 | 14 / 6 | |
| 5.0.0 | 14 / 6 | |
| 4.1.3 | 13 / 6 | |
| 4.1.2 | 14 / 6 | |
| 4.1.1 | 13 / 6 | |
| 4.1.0 | 13 / 6 | |
| 4.0.0 | 12 / 6 | |
| 3.0.1 | 12 / 6 | |
| 3.0.0 | 12 / 6 | |
| 2.5.0 | 10 / 6 | |
| 2.4.0 | 10 / 6 | |
| 2.3.0 | 9 / 5 | |
| 2.2.0 | 8 / 5 | |
| 2.1.0 | 8 / 5 | |
| 2.0.0 | 8 / 5 | |
| 1.0.3 | 8 / 6 | |
| 1.0.2 | 8 / 5 | |
| 1.0.1 | 7 / 5 | |
| 1.0.0 | 7 / 5 | |
| 0.7.0 | 8 / 3 | |
| 0.6.3 | 6 / 2 | |
| 0.6.2 | 6 / 2 | |
| 0.6.1 | 6 / 2 | |
| 0.6.0 | 7 / 2 | |
| 0.5.0 | 7 / 1 | |
| 0.4.0 | 7 / 1 | |
| 0.3.2 | 6 / 1 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.1 | 5 / 1 | |
| 0.2.0 | 5 / 1 | |
| 0.1.1 | 3 / 1 |
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-23. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-12-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-25. This could indicate a legitimate maintainer transition or an account compromise.
v2.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-06. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-18. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-02-13. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.