npm install @fig/complete-commander
88.3
Supply Chain Risk
96.7
Quality
82.7
Maintenance
100
Vulnerability
43 Stars
527 Commits
29 Forks
5 Watching
24 Branches
17 Contributors
Updated on 30 Sept 2024
Minified
Minified + Gzipped
TypeScript (91.75%)
JavaScript (2.81%)
Python (2.81%)
Go (2.56%)
Shell (0.05%)
Makefile (0.02%)
Cumulative downloads
Total Downloads
Last day
6.7%
32,663
Compared to previous day
Last week
7.1%
153,787
Compared to previous week
Last month
9.7%
675,976
Compared to previous month
Last year
4,609.8%
4,630,828
Compared to previous year
1
1
6
This repo contains the source for all of Fig tools related with autocomplete.
You can see the list of Fig's packages on the NPM registry here: https://www.npmjs.com/~withfig
You can see the source code and related README for each package in the ./packages
folder
create-completion-spec
@fig/publish-spec
@withfig/autocomplete-tools
@fig/eslint-config-autocomplete
@withfig/eslint-plugin-fig-linter
@fig/autocomplete-generators
@fig/autocomplete-hooks
@fig/autocomplete-helpers
argparse_complete_fig
cement_complete_fig
clap_complete_fig
click_complete_fig
cobracompletefig
@fig/complete-commander
@fig/complete-oclif
swift-argument-parser
@fig/autocomplete-merge
@fig/autocomplete-shared
@withfig/autocomplete-types
Update the package.json
version
propery
Commit the updated package.json
file to the origin repo
Git tag the commit you have just made using the following format and push the tag to the origin repo
<package_name>@<new_numerical_version>
git tag @fig/publish-spec@1.2.3
pnpm publish ./<package>
IMPORTANT: remember to tag the new package version following the current conventions (see the previous tags of a package) this is important for some workflows we are running and to keep track of when releases were done.
IMPORTANT: all packages need to be git tagged, not only npm ones!
e.g.
pnpm publish ./types
Note:
<workspace name>
is not the name of the folder, but the name specified inside the package.json of the package to publish.
@fig/complete[-_]($FRAMEWORK_NAME)
($FRAMEWORK_NAME)[-_]complete[-_]fig
According to language conventions you can use a dash or an underscore to separate the words.
Examples:
@fig/complete-commander
@fig/complete-oclif
clap_complete_fig
cobracompletefig
Most of our CLI integration tools allow to set the name of the subcommand added to the CLI but we also provide a default value for that.
That default name MUST be generate-fig-spec
such that running $CLI generate-fig-spec
prints the spec.
The functions exported from the integration can:
In all the cases the names are standardized and SHOULD be:
addCompletionSpecCommand
or createCompletionSpecCommand
for functions creating a new subcommandgenerateCompletionSpec
for functions that return the spec as a stringAccording to language conventions these function names can be transformed to snake case, etc...
If the CLI tool integration gets added directly to the module of the CLI tool itself and the CLI tool is configured using chained methods (e.g. yargs), then the chain method name SHOULD be:
.figCompletion()
public-site-nextjs
Docs MUST conform to the rules listed above too.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
6 existing vulnerabilities detected
Details
Reason
Found 0/5 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
branch protection not enabled on development/release branches
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-09-30
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