{"id":37162659,"url":"https://github.com/ooesili/vault","last_synced_at":"2026-01-14T19:21:22.430Z","repository":{"id":57561044,"uuid":"48624637","full_name":"ooesili/vault","owner":"ooesili","description":"A tool for managing secrets.","archived":false,"fork":true,"pushed_at":"2015-12-26T22:10:47.000Z","size":8339,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"master","last_synced_at":"2024-06-20T15:47:10.221Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://vaultproject.io","language":"Go","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"hashicorp/vault","license":"mpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ooesili.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":"audit/audit.go","citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-12-26T21:54:42.000Z","updated_at":"2024-06-20T15:47:10.223Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/ooesili/vault","commit_stats":null,"previous_names":[],"tags_count":11,"template":false,"template_full_name":null,"purl":"pkg:github/ooesili/vault","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ooesili%2Fvault","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ooesili%2Fvault/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ooesili%2Fvault/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ooesili%2Fvault/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ooesili","download_url":"https://codeload.github.com/ooesili/vault/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ooesili%2Fvault/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28432582,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-14T18:57:19.464Z","status":"ssl_error","status_checked_at":"2026-01-14T18:52:48.501Z","response_time":107,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-14T19:21:21.627Z","updated_at":"2026-01-14T19:21:22.377Z","avatar_url":"https://github.com/ooesili.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"Vault [![Build Status](https://travis-ci.org/hashicorp/vault.svg)](https://travis-ci.org/hashicorp/vault)\n=========\n**Please note**: We take Vault's security and our users' trust very seriously. If you believe you have found a security issue in Vault, _please responsibly disclose_ by contacting us at [security@hashicorp.com](mailto:security@hashicorp.com).\n\n=========\n\n-\tWebsite: https://www.vaultproject.io\n-\tIRC: `#vault-tool` on Freenode\n-\tMailing list: [Google Groups](https://groups.google.com/group/vault-tool)\n\n![Vault](https://raw.githubusercontent.com/hashicorp/vault/master/website/source/assets/images/logo-big.png?token=AAAFE8XmW6YF5TNuk3cosDGBK-sUGPEjks5VSAa2wA%3D%3D)\n\nVault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.\n\nA modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.\n\nThe key features of Vault are:\n\n* **Secure Secret Storage**: Arbitrary key/value secrets can be stored\n  in Vault. Vault encrypts these secrets prior to writing them to persistent\n  storage, so gaining access to the raw storage isn't enough to access\n  your secrets. Vault can write to disk, [Consul](https://www.consul.io),\n  and more.\n\n* **Dynamic Secrets**: Vault can generate secrets on-demand for some\n  systems, such as AWS or SQL databases. For example, when an application\n  needs to access an S3 bucket, it asks Vault for credentials, and Vault\n  will generate an AWS keypair with valid permissions on demand. After\n  creating these dynamic secrets, Vault will also automatically revoke them\n  after the lease is up.\n\n* **Data Encryption**: Vault can encrypt and decrypt data without storing\n  it. This allows security teams to define encryption parameters and\n  developers to store encrypted data in a location such as SQL without\n  having to design their own encryption methods.\n\n* **Leasing and Renewal**: All secrets in Vault have a _lease_ associated\n  with it. At the end of the lease, Vault will automatically revoke that\n  secret. Clients are able to renew leases via built-in renew APIs.\n\n* **Revocation**: Vault has built-in support for secret revocation. Vault\n  can revoke not only single secrets, but a tree of secrets, for example\n  all secrets read by a specific user, or all secrets of a particular type.\n  Revocation assists in key rolling as well as locking down systems in the\n  case of an intrusion.\n\nFor more information, see the [introduction section](https://www.vaultproject.io/intro)\nof the Vault website.\n\nGetting Started \u0026 Documentation\n-------------------------------\n\nAll documentation is available on the [Vault website](https://www.vaultproject.io).\n\nDeveloping Vault\n--------------------\n\nIf you wish to work on Vault itself or any of its built-in systems,\nyou'll first need [Go](https://www.golang.org) installed on your\nmachine (version 1.5+ is *required*).\n\nFor local dev first make sure Go is properly installed, including setting up a\n[GOPATH](https://golang.org/doc/code.html#GOPATH). After setting up Go, you can\ndownload the required build tools such as vet, cover, godep etc by bootstrapping\nyour environment. \n\n```sh\n$ make bootstrap\n...\n```\n\nNext, clone this repository into `$GOPATH/src/github.com/hashicorp/vault`.\nThen type `make`. This will run the tests. If this exits with exit status 0,\nthen everything is working!\n\n```sh\n$ make\n...\n```\n\nTo compile a development version of Vault, run `make dev`. This will put the\nVault binary in the `bin` and `$GOPATH/bin` folders:\n\n```sh\n$ make dev\n...\n$ bin/vault\n...\n```\n\nIf you're developing a specific package, you can run tests for just that\npackage by specifying the `TEST` variable. For example below, only\n`vault` package tests will be run.\n\n```sh\n$ make test TEST=./vault\n...\n```\n\n### Acceptance Tests\n\nVault has comprehensive [acceptance tests](https://en.wikipedia.org/wiki/Acceptance_testing)\ncovering most of the features of the secret and auth backends.\n\nIf you're working on a feature of a secret or auth backend and want to\nverify it is functioning (and also hasn't broken anything else), we recommend\nrunning the acceptance tests.\n\n**Warning:** The acceptance tests create/destroy/modify *real resources*, which\nmay incur real costs in some cases. In the presence of a bug, it is technically\npossible that broken backends could leave dangling data behind. Therefore,\nplease run the acceptance tests at your own risk. At the very least,\nwe recommend running them in their own private account for whatever backend\nyou're testing.\n\nTo run the acceptance tests, invoke `make testacc`:\n\n```sh\n$ make testacc TEST=./builtin/logical/consul\n...\n```\n\nThe `TEST` variable is required, and you should specify the folder where the\nbackend is. The `TESTARGS` variable is recommended to filter down to a specific\nresource to test, since testing all of them at once can sometimes take a very\nlong time.\n\nAcceptance tests typically require other environment variables to be set for\nthings such as access keys. The test itself should error early and tell\nyou what to set, so it is not documented here.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fooesili%2Fvault","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fooesili%2Fvault","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fooesili%2Fvault/lists"}