VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cryptiles: vulnerability history, versions and safety

cryptiles is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 11 releases, first recorded in Sep 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cryptiles vulnerabilities

Vulert verdict on cryptiles 4.1.3 i

Updated on 23 Oct 2026

Good news: 4.1.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

What to do: Stay on 4.1.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.1.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 11 Sep 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1,102 packages i
  • Stars 184 i
  • OpenSSF scorecard 3/10 i
  • Last release 95 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for cryptiles, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.2.1 03 Jan 2024 C1 non-standard Yes Details →
3.1.4 05 Nov 2018 C1 BSD-3-Clause Yes Details →
4.1.3 03 Nov 2018 none BSD-3-Clause — Details →
3.1.3 02 Nov 2018 C1 BSD-3-Clause Yes Details →
4.1.2 24 Jun 2018 none BSD-3-Clause — Details →
4.1.1 10 Nov 2017 C1 BSD-3-Clause Yes Details →
4.1.0 03 Nov 2017 C1 BSD-3-Clause Yes Details →
4.0.2 03 Nov 2017 C1 BSD-3-Clause Yes Details →
4.0.1 26 Sep 2017 C1 BSD-3-Clause Yes Details →
4.0.0 24 Sep 2017 C1 BSD-3-Clause Yes Details →
3.1.2 28 May 2017 C1 BSD-3-Clause Yes Details →
3.1.1 05 Sep 2016 C1 BSD-3-Clause Yes Details →
3.1.0 05 Sep 2016 C1 BSD-3-Clause Yes Details →
3.0.2 27 Jul 2016 none BSD-3-Clause — Details →
3.0.1 19 May 2016 none BSD-3-Clause — Details →
3.0.0 02 Nov 2015 none BSD-3-Clause — Details →
2.0.5 09 Sep 2015 none BSD-3-Clause — Details →
2.0.4 15 Sep 2014 none BSD-3-Clause — Details →
2.0.3 05 Sep 2014 none BSD-3-Clause — Details →
2.0.2 02 Aug 2014 none BSD-3-Clause — Details →
2.0.1 08 Apr 2014 none BSD-3-Clause — Details →
2.0.0 31 Dec 2013 none BSD-3-Clause — Details →
1.0.1 29 Sep 2013 none BSD-3-Clause — Details →
1.0.0 10 Sep 2013 none BSD-3-Clause — Details →
0.2.2 03 Jul 2013 none BSD-3-Clause — Details →
0.2.1 30 Apr 2013 none BSD-3-Clause — Details →
0.2.0 05 Apr 2013 none BSD-3-Clause — Details →
0.1.3 18 Mar 2013 none BSD-3-Clause — Details →
0.1.2 17 Feb 2013 none BSD-3-Clause — Details →
0.1.1 17 Feb 2013 none BSD-3-Clause — Details →
0.1.0 08 Feb 2013 none BSD-3-Clause — Details →
0.0.2 07 Feb 2013 none BSD-3-Clause — Details →
0.0.1 13 Jan 2013 none BSD-3-Clause — Details →

All 33 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cryptiles

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000620: Insufficient Entropy in cryptiles 9.8 critical 4.1.2 11 Sep 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About cryptiles

Is cryptiles safe to use?

Vulert records 1 vulnerabilities for cryptiles in npm: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is cryptiles's Vulert package health score?

Vulert scores cryptiles 45/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of cryptiles affected?

No. 4.1.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of cryptiles should I use?

4.1.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does cryptiles have?

1 vulnerability is recorded for cryptiles in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cryptiles vulnerabilities disclosed?

0 vulnerabilities were recorded for cryptiles in the last 12 months, and the oldest entry in this database dates to 11 Sep 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cryptiles are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor cryptiles for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cryptiles version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.