a13n
Build AI agents and run them on cloud.
Registry mapping Go module paths to the NuGet packages of their go2cs C# conversions
Translation pending
Developer toolsGoGitHub @ritchiecarrollOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗nugetgo is a registry that maps Go module paths to the NuGet package IDs of their
go2cs C# conversions. go2cs transpiles Go to C#; with a
mapping, a converted program can reference a dependency as a published NuGet package instead of
converting it again. go2cs -recurse=nuget consults the registry by default; see
Mapping modules to NuGet packages
in the go2cs README.
The registry is one plain text file, served at:
https://nugetgo.net/v1/mappings.txt
The site at nugetgo.net is generated from that file and lists its mappings. The file is the single source of truth.
The current mappings are listed at nugetgo.net.
One mapping per line, six TAB-separated fields, # for comments:
module-path nuget-id status source-repo registered contact
module-path: the Go module path as in go.mod, including any /vN suffix; one row per major version.nuget-id: the NuGet package ID of the conversion, nugetgo. followed by the dotted module path
(github.com/example/widget/v2 maps to nugetgo.github.com.example.widget.v2) or a
hash-shortened alternate when that ID cannot be used, whoever publishes it, the module's own
author included. A module conversion does not take the go. prefix, which go2cs uses for the
converted Go standard library.status: canonical (the package's repository metadata points to the module's own org),
community (a third-party conversion), or withdrawn (kept for the record, treated as unmapped).source-repo, registered, contact: provenance for people.The file maps names only. Package versions are not listed; each package describes the Go module version it was converted from.
Mappings are added by pull request. CONTRIBUTING.md has the trust policy, the NuGet package ID pattern and the checks every row goes through.
CI lints the whole file on every pull request. For each row a pull request adds or changes, it
verifies that the module resolves at proxy.golang.org, that the package resolves at nuget.org,
that the package's repository metadata confirms or contradicts the row's claimed status, and that
the package's go2cs self-description names the module, a real module version and a known go2cs
release. Nothing merges automatically; a maintainer merges every pull request.
nugetgo is not a package host (nuget.org hosts the packages) and not a build service. It maps names and checks provenance; it makes no claim about package content.
The data and the site generator are dedicated to the public domain under CC0-1.0.