cli,outdated: default homepage to an empty string by anchnk · Pull Request #124 · npm/cli

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk · 2018-12-17T17:24:00Z

This patch default package's homepage to an empty string in case the
homepage isn't specificied in the package manifest.

Before this patch, if at least one package didn't set an associated
homepage, running npm outdated --long would break.

After this patch, it won't display anything for this specific package
Homepage row and it won't break for the other packages.

This patch default package's homepage to an empty string in case the homepage isn't specificied in the package manifest. Before this patch, if at least one package didn't set an associated homepage, running npm outdated --long would break. After this patch, it won't display anything for this specific package Homepage row and it won't break for the other packages.

zkat

Thanks for this patch!

@anchnk

PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

…pm#124) Replaced silent `let _ =` on set_permissions calls in save_encrypted with eprintln! warnings so users are aware if their credential files end up with insecure permissions. Also log keyring access failures instead of silently falling through to file storage.

anchnk requested a review from a team as a code owner December 17, 2018 17:24

zkat approved these changes Dec 17, 2018
View reviewed changes

zkat changed the base branch from latest to release-nextDecember 17, 2018 17:39

zkat added the semver:patch semver patch level for changes label Dec 17, 2018

fharper approved these changes Dec 17, 2018
View reviewed changes

aeschright merged commit a5c9e6f into npm:release-nextJan 9, 2019

aeschright pushed a commit that referenced this pull request Jan 18, 2019
cli,outdated: default homepage to an empty string (#124)
80957dd
PR-URL: #124 Credit: @anchnk Reviewed-By: @aeschright

larsgw mentioned this pull request Jan 18, 2019
update: re-enable updating local packages #73
Closed

snyk-bot mentioned this pull request May 11, 2022
[Snyk] Upgrade read-package-json from 5.0.0 to 5.0.1 Mhmonicox/cli#3
Open

Mhmonicox mentioned this pull request Feb 15, 2023
[Snyk] Upgrade cacache from 16.0.4 to 16.1.3 Mhmonicox/cli#9
Open

Mhmonicox mentioned this pull request Jun 1, 2023
[Snyk] Upgrade cacache from 16.0.4 to 16.1.3 Mhmonicox/cli#14
Open

CALISOULB mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#19
Open

This was referenced Nov 30, 2023
[Snyk] Security upgrade npm-registry-fetch from 9.0.0 to 14.0.0 varmakarthik12/cli#28
Closed
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#30
Closed
[Snyk] Security upgrade npm-registry-fetch from 9.0.0 to 14.0.0 varmakarthik12/cli#31
Closed

bumplzz69 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities bumplzz69/cli#38
Open

mtdev2 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities mtdev2/cli#91
Open

Bhanditz mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities Bhanditz/cli#29
Open

varmakarthik12 mentioned this pull request Nov 30, 2023
[Snyk] Fix for 1 vulnerabilities varmakarthik12/cli#38
Closed

baby636 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities baby636/cli#62
Open

varmakarthik12 mentioned this pull request Dec 1, 2023
[Snyk] Security upgrade npm-registry-fetch from 9.0.0 to 14.0.0 varmakarthik12/cli#42
Closed

kevinjm39 mentioned this pull request Dec 19, 2023
[Snyk] Fix for 1 vulnerabilities kevinjm39/cli#19
Open

MrBrain295 mentioned this pull request Dec 19, 2023
[Snyk] Fix for 3 vulnerabilities MrBrain295/cli#12
Open

CALISOULB mentioned this pull request Dec 20, 2023
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#21
Open

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 2, 2026
🤖 봇 응답 (npm#124)
f774f7e

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 3, 2026
📊 대시보드 데이터 업데이트 (npm#124)
3f3e1cb

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 14, 2026
🔧 자동 수리 완료 (npm#124)
f89af5c

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 8, 2026
🔥 트렌드 선점 후보 갱신 (npm#124)
0a54d18