npm · npm:secure-keys
secure-keys active
Encrypt/Decrypt the values of a given object
The latest stable version of secure-keys is 1.0.0, published on 2016-02-02. Verified by Vigia on 2026-11-12.
| Latest stable version | 1.0.0 |
|---|---|
| Published | 2016-02-02 06:11:56 UTC |
| Install | npm install secure-keys@latest |
| Requires (engines) | none declared |
| Peer dependencies | — |
| Dist-tags | latest: 1.0.0 |
| License | MIT |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 12:44:10 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Ask your AI assistant to check this
AI models are trained up to a date, so they can be wrong about versions, deprecations and vulnerabilities. Paste this into Claude, ChatGPT, Perplexity or Cursor and it will answer with the verified data on this page:
Before answering about the npm package "secure-keys", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/secure-keys . For my whole project use https://vigia.coredls.cloud/context
Using an AI coding agent every day? Connect Vigia once and it checks this by itself.
Maintenance
| Activity | dormant |
|---|---|
| Last stable release | 2016-02-02 06:11:56 UTC · 3936 days ago |
| Stable releases in the last 12 months | 0 |
| Published versions | 1 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
1.0.0 | 2016-02-02 06:11:56 UTC |
Showing the 1 most recent of 1 versions. JSON
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What is the latest version of secure-keys?
The latest stable version of secure-keys is 1.0.0, published on 2016-02-02. Verified by Vigia on 2026-11-12.
How do I install the latest version of secure-keys?
Run npm install secure-keys@latest. The latest stable version is 1.0.0 (verified 2026-11-12).
Is secure-keys deprecated?
No. secure-keys is not marked as deprecated in the registry.
Which Node.js version does secure-keys require?
secure-keys 1.0.0 does not declare a Node.js version requirement.
Does secure-keys 1.0.0 have known vulnerabilities?
No known advisories affect secure-keys 1.0.0 according to the data Vigia checks.
Is secure-keys still maintained?
secure-keys published 0 stable releases in the last 12 months; the most recent was 3936 days ago. Activity: dormant.
Observed changes
No changes observed yet since Vigia started tracking this package.
Related packages
- verdaccio-audit
- @stryker-mutator/api
- expo-doctor
- @oxc-parser/binding-darwin-x64
- lifecycle-utils
- @types/flat
- @walletconnect/ethereum-provider
- @styled-system/flexbox
- react-window-infinite-loader
- url-value-parser
- @babel/helper-regex
- @hotwired/turbo-rails
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/secure-keys) [](https://vigia.coredls.cloud/npm/secure-keys) [](https://vigia.coredls.cloud/npm/secure-keys)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/secure-keys
GET https://vigia.coredls.cloud/v1/packages/npm/secure-keys/versions/{version}