Package Health Score

68 / 100

security
No known security issues
popularity
Limited
maintenance
Sustainable
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
1.3.35	\|	10/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.1	\|	03/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.13.3	\|	01/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.12.1	\|	11/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.11.0	\|	09/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (778)

GitHub Stars: 567
Forks: 30
Contributors: 30

Direct Usage Popularity

The npm package coc-go receives a total of 778 downloads a week. As such, we scored coc-go popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package coc-go, we found that it has been starred 567 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 30
Funding: No

With more than 10 contributors for the coc-go repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like coc-go is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 10
Open PR: 1
Last Release: 1 month ago
Last Commit: 1 month ago

Further analysis of the maintenance status of coc-go based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that coc-go demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=16

Age: 6 years
Dependencies: 4 Direct
Versions: 70
Install Size: 130 kB
Dist-tags: 1
# of Files: 22
Maintainers: 1
TS Typings: No

coc-go has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

coc-go

Go language server extension using gopls for coc.nvim.

Install

In your vim/neovim, run this command:

:CocInstall coc-go

Features

See gopls

Commands

Additional to commands provided by gopls, this extensions provides these commands:

Key	Description
`go.gopls.tidy`	Run gopls.tidy LSP command
`go.impl.cursor`	Generate interface stubs
`go.install.gomodifytags`	Install / update gomodifytags
`go.install.goplay`	Install / update goplay
`go.install.gopls`	Install / update gopls
`go.install.gotests`	Install / update gotests
`go.install.impl`	Install / update impl
`go.install.tools`	Install / update all tools
`go.playground`	Run on go playground
`go.tags.add`	Add tags to struct fields
`go.tags.add.line`	Add tags to struct field in current line
`go.tags.add.prompt`	Add tags to struct fields (prompt)
`go.tags.clear`	Remove all tags from struct fields
`go.tags.clear.line`	Remove all tags from struct fields in current line
`go.tags.remove`	Remove tags from struct fields
`go.tags.remove.line`	Remove tags from struct field in current line
`go.tags.remove.prompt`	Remove tags from struct fields (prompt)
`go.test.generate.exported`	Generate unit tests for exported functions in file
`go.test.generate.file`	Generate unit tests for file
`go.test.generate.function`	Generate unit tests for current function
`go.test.toggle`	Toggle test file
`go.version`	Print extension version

Examples

Add or Remove specific tags

CocCommand go.tags.add yaml
CocCommand go.tags.add yaml json xml
CocCommand go.tags.remove xml

Add missing imports on save

autocmd BufWritePre *.go :silent call CocAction('runCommand', 'editor.action.organizeImport')

Map Keys to command

autocmd FileType go nmap gtj :CocCommand go.tags.add json
autocmd FileType go nmap gty :CocCommand go.tags.add yaml
autocmd FileType go nmap gtx :CocCommand go.tags.clear

Snippets

Snippets are imported from golang/vscode-go and require coc-snippets to be installed.

Configuration options

Key	Description	Default
`go.checkForUpdates`	Check for gopls updates on start.	install
`go.disable`	Disable gopls features	{}
‣ `completion`	Disable completion feature (Change requires `:CocRestart`)	false
‣ `diagnostics`	Disable handle diagnostics (Change requires `:CocRestart`)	false
‣ `features`	Disabled features (Change requires `:CocRestart`)	[]
‣ `snippetCompletion`	Disable snippet completion (Change requires `:CocRestart`)	false
‣ `workspaceFolders`	Disable workspaceFolders feature (Change requires `:CocRestart`)	false
`go.enable`	Enable Go extension	true
`go.goplsArgs`	Arguments passed to `gopls` (Change requires `:CocRestart`)
`go.goplsEnv`	ENV passed to `gopls` (Change requires `:CocRestart`)
`go.goplsOptions`	See `gopls` documentation
‣ `allowImplicitNetworkAccess`	This setting is experimental and may be deleted. allowImplicitNetworkAccess disables GOPROXY=off, allowing implicit module downloads rather than requiring user action.	false
‣ `analyses`	analyses specify analyses that the user would like to enable or disable.
‣ `analysisProgressReporting`	analysisProgressReporting controls whether gopls sends progress notifications when construction of its index of analysis facts is taking a long time.	true
‣ `annotations`	This setting is experimental and may be deleted. annotations specifies the various kinds of optimization diagnostics that should be reported by the gc_details command.
‣ `buildFlags`	buildFlags is the set of flags passed on to the build system when invoked.
‣ `codelenses`	codelenses overrides the enabled/disabled state of each of gopls' sources of Code Lenses.
‣ `completeFunctionCalls`	completeFunctionCalls enables function call completion.	true
‣ `completionBudget`	This setting is for debugging purposes only. completionBudget is the soft latency goal for completion requests.	100ms
‣ `diagnosticsDelay`	This is an advanced setting and should not be configured by most `gopls` users. diagnosticsDelay controls the amount of time that gopls waits after the most recent file modification before computing deep diagnostics.	1s
‣ `diagnosticsTrigger`	This setting is experimental and may be deleted. diagnosticsTrigger controls when to run diagnostics.	Edit
‣ `directoryFilters`	directoryFilters can be used to exclude unwanted directories from the workspace.
‣ `env`	env adds environment variables to external commands run by `gopls`, most notably `go list`.
‣ `expandWorkspaceToModule`	This setting is experimental and may be deleted. expandWorkspaceToModule determines which packages are considered "workspace packages" when the workspace is using modules.	true
‣ `experimentalPostfixCompletions`	This setting is experimental and may be deleted. experimentalPostfixCompletions enables artificial method snippets such as "someSlice.sort!".	true
‣ `gofumpt`	gofumpt indicates if we should run gofumpt formatting.	false
‣ `hints`	This setting is experimental and may be deleted. hints specify inlay hints that users want to see.
‣ `hoverKind`	hoverKind controls the information that appears in the hover text.	FullDocumentation
‣ `importShortcut`	importShortcut specifies whether import statements should link to documentation or go to definitions.	Both
‣ `linkTarget`	linkTarget is the base URL for links to Go package documentation returned by LSP operations such as Hover and DocumentLinks and in the CodeDescription field of each Diagnostic.	pkg.go.dev
‣ `linksInHover`	linksInHover controls the presence of documentation links in hover markdown.	true
‣ `local`	local is the equivalent of the `goimports -local` flag, which puts imports beginning with this string after third-party packages.
‣ `matcher`	This is an advanced setting and should not be configured by most `gopls` users. matcher sets the algorithm that is used when calculating completion candidates.	Fuzzy
‣ `memoryMode`	This setting is experimental and may be deleted. obsolete, no effect
‣ `noSemanticNumber`	This setting is experimental and may be deleted. noSemanticNumber turns off the sending of the semantic token 'number'	false
‣ `noSemanticString`	This setting is experimental and may be deleted. noSemanticString turns off the sending of the semantic token 'string'	false
‣ `semanticTokens`	This setting is experimental and may be deleted. semanticTokens controls whether the LSP server will send semantic tokens to the client.	false
‣ `standaloneTags`	standaloneTags specifies a set of build constraints that identify individual Go source files that make up the entire main package of an executable.
‣ `staticcheck`	This setting is experimental and may be deleted. staticcheck enables additional analyses from staticcheck.io.	false
‣ `symbolMatcher`	This is an advanced setting and should not be configured by most `gopls` users. symbolMatcher sets the algorithm that is used when finding workspace symbols.	FastFuzzy
‣ `symbolScope`	symbolScope controls which packages are searched for workspace/symbol requests.	all
‣ `symbolStyle`	This is an advanced setting and should not be configured by most `gopls` users. symbolStyle controls how symbols are qualified in symbol responses.	Dynamic
‣ `templateExtensions`	templateExtensions gives the extensions of file names that are treated as template files.
‣ `usePlaceholders`	placeholders enables placeholders for function parameters or struct fields in completion responses.	false
‣ `verboseOutput`	This setting is for debugging purposes only. verboseOutput enables additional debug logging.	false
‣ `vulncheck`	This setting is experimental and may be deleted. vulncheck enables vulnerability scanning.	Off
`go.goplsPath`	Path to `gopls` bin (Change requires `:CocRestart`)
`go.goplsUseDaemon`	Run gopls as daemon	true
`go.tags`
‣ `options`	Comma separated tag=options pairs to be used by `go.tags.add` command	json=omitempty
‣ `skipUnexported`	If true, skip unexported fields	false
‣ `tags`	Comma separated tags to be used by `go.tags.add` command	json
‣ `transform`	Transformation rule used by `go.tags.add` command to add tags	snakecase
`go.tests`
‣ `generateFlags`	Additional command line flags to pass to `gotests` for generating tests.	[]
`go.trace.server`	Trace level of gopls	off

Trigger completion in coc-settings.json to get complete list.

Example Configuration

{
  "go.goplsOptions": {
    "completeUnimported": true
  }
}

Development

Run npm run build or npm run build:watch
Link extension: npm run link / npm run unlink

Tools

FAQ

How does `coc-go` compare to `vim-go`?

With coc-go I do not aim to recreate the features of vim-go. For now, the main goal is to provide a convenient way to install gopls and use it with coc.nvim.

If you need more than the features provided by gopls, you are probably better of with vim-go or govim.

How to use `coc-go` with wasm?

Add this to you (local) coc-settings.json (run :CocLocalConfig).

{
  "go.goplsEnv": {
    "GOOS": "js",
    "GOARCH": "wasm",
  }
}

Running `gopls` as a daemon

coc-go runs gopls as shared daemon by passing -remote=auto to gopls. To disable this behavior set go.goplsUseDaemon to false.

See Running gopls as a daemon for more information.

License

coc-go dependencies

tslib vscode-languageserver-textdocument vscode-uri which

coc-go development dependencies

@types/jest @types/node @types/tmp @types/which @typescript-eslint/eslint-plugin @typescript-eslint/parser coc.nvim eslint eslint-config-josa-typescript jest rimraf tmp ts-jest typescript

FAQs

What is coc-go?

gopls extension for coc. Visit Snyk Advisor to see a full health score report for coc-go, including popularity, security, maintenance & community analysis.

Is coc-go popular?

The npm package coc-go receives a total of 778 weekly downloads. As such, coc-go popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is coc-go well maintained?

We found indications that coc-go maintenance is sustainable demonstrating some project activity. We saw a total of 30 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is coc-go safe to use?

The npm package coc-go was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 November-2024, at 23:28 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (778)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

coc-go

Install

Features

Commands

Examples

Snippets

Configuration options

Example Configuration

Development

Tools

FAQ

How does coc-go compare to vim-go?

How to use coc-go with wasm?

Running gopls as a daemon

License

coc-go dependencies

coc-go development dependencies

FAQs

What is coc-go?

Is coc-go popular?

Is coc-go well maintained?

Is coc-go safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues

How does `coc-go` compare to `vim-go`?

How to use `coc-go` with wasm?

Running `gopls` as a daemon