Gathering detailed insights and metrics for @expo/plugin-warn-if-update-available
Gathering detailed insights and metrics for @expo/plugin-warn-if-update-available
Gathering detailed insights and metrics for @expo/plugin-warn-if-update-available
Gathering detailed insights and metrics for @expo/plugin-warn-if-update-available
warn user if a new CLI version is available
npm install @expo/plugin-warn-if-update-available
Typescript
Module System
Min. Node Version
Node Version
NPM Version
71.7
Supply Chain
84.5
Quality
80.8
Maintenance
100
Vulnerability
99.3
License
TypeScript (93.22%)
JavaScript (6%)
Batchfile (0.78%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
38 Stars
949 Commits
14 Forks
2 Watchers
15 Branches
18 Contributors
Updated on Jul 14, 2025
Latest Version
2.5.1
Package Id
@expo/plugin-warn-if-update-available@2.5.1
Unpacked Size
9.34 kB
Size
3.89 kB
File Count
10
NPM Version
8.11.0
Node Version
16.15.1
Published on
Aug 17, 2023
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
warns if there is a newer version of CLI released
This plugin shows a warning message if a user is running an out of date CLI.
This checks the version against the npm registry asynchronously in a forked process, at most once per 7 days. It then saves a version file to the cache directory that will enable the warning. The upside of this method is that it won't block a user while they're using your CLI—the downside is that it will only display after running a command that fetches the new version.
Add the plugin to your project with yarn add @oclif/plugin-warn-if-update-available
, then add it to the package.json
of the oclif CLI:
1{ 2 "name": "mycli", 3 "version": "0.0.0", 4 // ... 5 "oclif": { 6 "plugins": ["@oclif/plugin-help", "@oclif/plugin-warn-if-update-available"] 7 } 8}
In package.json
, set oclif['warn-if-update-available']
to an object with
any of the following configuration properties:
timeoutInDays
- Duration between update checks. Defaults to 60.message
- Customize update message.registry
- URL of registry. Defaults to the public npm registry: https://registry.npmjs.org
authorization
- Authorization header value for registries that require auth.1{ 2 "oclif": { 3 "plugins": [ 4 "@oclif/plugin-warn-if-update-available" 5 ], 6 "warn-if-update-available": { 7 "timeoutInDays": 7, 8 "message": "<%= config.name %> update available from <%= chalk.greenBright(config.version) %> to <%= chalk.greenBright(latest) %>.", 9 "registry": "https://my.example.com/module/registry", 10 "authorization": "Basic <SOME READ ONLY AUTH TOKEN>" 11 } 12 } 13}
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
Found 0/3 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More