npm · npm:crypto
crypto deprecated
This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name.
The latest stable version of crypto is 1.0.1, published on 2017-08-10. Verified by Vigia on 2026-11-12.
| Latest stable version | 1.0.1 |
|---|---|
| Published | 2017-08-10 22:43:43 UTC |
| Install | npm install crypto@latest |
| Deprecation | This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. |
| Requires (engines) | none declared |
| Peer dependencies | — |
| Dist-tags | latest: 1.0.1 |
| License | ISC |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 12:27:24 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 "crypto", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/crypto . 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 | 2017-08-10 22:43:43 UTC · 3380 days ago |
| Stable releases in the last 12 months | 0 |
| Published versions | 4 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
1.0.1 withdrawn | 2017-08-10 22:43:43 UTC |
1.0.0 withdrawn | 2017-08-10 22:32:46 UTC |
0.0.3 withdrawn | 2011-11-08 17:53:56 UTC |
0.0.1 withdrawn | 2011-04-14 15:34:54 UTC |
Showing the 4 most recent of 4 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 crypto?
The latest stable version of crypto is 1.0.1, published on 2017-08-10. Verified by Vigia on 2026-11-12.
How do I install the latest version of crypto?
Run npm install crypto@latest. The latest stable version is 1.0.1 (verified 2026-11-12).
Is crypto deprecated?
Yes. The registry marks crypto as deprecated. Message from the maintainers: "This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in."
Which Node.js version does crypto require?
crypto 1.0.1 does not declare a Node.js version requirement.
Does crypto 1.0.1 have known vulnerabilities?
No known advisories affect crypto 1.0.1 according to the data Vigia checks.
Is crypto still maintained?
crypto published 0 stable releases in the last 12 months; the most recent was 3380 days ago. Activity: dormant.
Observed changes
No changes observed yet since Vigia started tracking this package.
Related packages
- @react-types/autocomplete
- @lovable.dev/cloud-auth-js
- @livekit/mutex
- lodash._basetostring
- @rc-component/async-validator
- @google-cloud/cloud-sql-connector
- boundary
- weak-map
- rslog
- @csstools/postcss-contrast-color-function
- mjml-parser-xml
- otpauth
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/crypto) [](https://vigia.coredls.cloud/npm/crypto) [](https://vigia.coredls.cloud/npm/crypto)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/crypto
GET https://vigia.coredls.cloud/v1/packages/npm/crypto/versions/{version}