
Research
Security News
The Growing Risk of Malicious Browser Extensions
Socket researchers uncover how browser extensions in trusted stores are used to hijack sessions, redirect traffic, and manipulate user behavior.
github.com/mongodb/mongo-tools
Report any bugs, improvements, or new feature requests at https://jira.mongodb.org/browse/TOOLS
We currently build the tools with Go version 1.15. Other Go versions may work but they are untested.
Using go get
to directly build the tools will not work. To build them, it's recommended to first
clone this repository:
git clone https://github.com/mongodb/mongo-tools
cd mongo-tools
Then run ./make build
to build all the tools, placing them in the bin
directory inside the
repository. Run ./bin/mongodump --help
to verify that the built binary works.
You can also build a subset of the tools using the -pkgs
option. For example,
./make build -pkgs=mongodump,mongorestore
builds only mongodump
and mongorestore
.
To use the build/test scripts in this repository, you must set GOROOT to your Go root directory. This may depend on how you installed Go.
export GOROOT=/usr/local/go
When running the built binaries, if the process gets killed immediately and you see the following
output:
zsh: killed ./bin/mongodump --help
Then you need to sign the binary in order to run it:
codesign --force --sign - bin/mongodump
You can also choose to configure the security policy of the terminal application so that signing is
not required:
(in macOS Sonoma) System Settings > Privacy & Security > Developer Tools
Starting with version 100.3.1, the tools use go mod
to manage dependencies. All dependencies are
listed in the go.mod
file and are directly vendored in the vendor
directory.
In order to make changes to dependencies, you first need to change the go.mod
file. You can
manually edit that file to add/update/remove entries, or you can run the following in the repository
directory:
go mod edit -require=<package>@<version> # for adding or updating a dependency
go mod edit -droprequire=<package> # for removing a dependency
Then run go mod vendor -v
to reconstruct the vendor
directory to match the changed go.mod
file.
Optionally, run go mod tidy -v
to ensure that the go.mod
file matches the mongo-tools
source
code.
See our Contributor's Guide.
See the MongoDB packages documentation.
For documentation on older versions of the MongoDB, reference that version of the MongoDB Server Manual:
See our Adding New Platform Support Guide.
See our Vendor the Change into Server Repo.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover how browser extensions in trusted stores are used to hijack sessions, redirect traffic, and manipulate user behavior.
Research
Security News
An in-depth analysis of credential stealers, crypto drainers, cryptojackers, and clipboard hijackers abusing open source package registries to compromise Web3 development environments.
Security News
pnpm 10.12.1 introduces a global virtual store for faster installs and new options for managing dependencies with version catalogs.