Vulnerability Database · Hex · Package report

credo: vulnerability history, versions and safety

Q: How do I monitor credo for upcoming vulnerabilities?

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

credo is a package in the Hex ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Hex ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all credo vulnerabilities

Vulert verdict on credo 1.7.19 i

Updated on 23 Oct 2026

Good news: 1.7.19, the version you would install today, has no known vulnerabilities.

Package health score 96/100

Security No known security issues
Maintenance Sustainable
Popularity Key ecosystem project
Community Not enough data

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

Current release 1.7.19 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 93,667,838 packages i
Last release 4 months ago i

Version list, release dates, licence and dependants published by hex.pm, 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for credo, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
1.7.19	05 Jun 2026	none	—	—	Details →
1.7.18	10 Apr 2026	none	—	—	Details →
1.7.17	03 Mar 2026	none	—	—	Details →
1.7.16	27 Jan 2026	none	—	—	Details →
1.7.15	26 Dec 2025	none	—	—	Details →
1.7.14	01 Dec 2025	none	—	—	Details →
1.7.13	15 Oct 2025	none	—	—	Details →
1.7.12	17 Apr 2025	none	—	—	Details →
1.7.11	28 Dec 2024	none	—	—	Details →
1.7.10	04 Nov 2024	none	—	—	Details →
1.7.9	03 Nov 2024	none	—	—	Details →
1.7.8	26 Sep 2024	none	—	—	Details →
1.7.7	12 Jun 2024	none	—	—	Details →
1.7.7-rc.0	02 Jun 2024	none	—	—	Details →
1.7.6	09 May 2024	none	—	—	Details →
1.7.5	22 Feb 2024	none	—	—	Details →
1.7.4	08 Feb 2024	none	—	—	Details →
1.7.3	05 Jan 2024	none	—	—	Details →
1.7.2	22 Dec 2023	none	—	—	Details →
1.7.2-rc.4	21 Dec 2023	none	—	—	Details →
1.7.2-rc.3	18 Dec 2023	none	—	—	Details →
1.7.2-rc.2	07 Dec 2023	none	—	—	Details →
1.7.2-rc.1	05 Dec 2023	none	—	—	Details →
1.7.2-rc.0	16 Nov 2023	none	—	—	Details →
1.7.1	01 Oct 2023	none	—	—	Details →
1.7.0	20 Mar 2023	none	—	—	Details →
1.7.0-rc.2	04 Feb 2023	none	—	—	Details →
1.7.0-rc.1	31 Dec 2022	none	—	—	Details →
1.6.7	02 Sep 2022	none	—	—	Details →
1.6.6	31 Jul 2022	none	—	—	Details →
1.6.5	16 Jul 2022	none	—	—	Details →
1.6.4	27 Feb 2022	none	—	—	Details →
1.6.3	08 Feb 2022	none	—	—	Details →
1.6.2	17 Jan 2022	none	—	—	Details →
1.6.1	19 Nov 2021	none	—	—	Details →
1.6.0	17 Nov 2021	none	—	—	Details →
1.6.0-rc.1	24 Sep 2021	none	—	—	Details →
1.6.0-rc.0	11 Sep 2021	none	—	—	Details →
1.5.6	04 Jun 2021	none	—	—	Details →
1.5.5	06 Feb 2021	none	—	—	Details →
1.5.4	26 Dec 2020	none	—	—	Details →
1.5.3	11 Dec 2020	none	—	—	Details →
1.5.2	07 Dec 2020	none	—	—	Details →
1.5.1	08 Nov 2020	none	—	—	Details →
1.5.0	28 Oct 2020	none	—	—	Details →
1.5.0-rc.5	26 Oct 2020	none	—	—	Details →
1.5.0-rc.4	11 Oct 2020	none	—	—	Details →
1.5.0-rc.3	09 Oct 2020	none	—	—	Details →
1.5.0-rc.2	22 Sep 2020	none	—	—	Details →
1.5.0-rc.1	21 Sep 2020	none	—	—	Details →
1.4.1	07 Oct 2020	none	—	—	Details →
1.4.0	19 Apr 2020	none	—	—	Details →
1.4.0-rc.2	10 Apr 2020	none	—	—	Details →
1.4.0-rc.1	02 Apr 2020	none	—	—	Details →
1.3.2	27 Mar 2020	none	—	—	Details →
1.3.1	14 Mar 2020	none	—	—	Details →
1.3.0	09 Mar 2020	none	—	—	Details →
1.3.0-rc3	01 Mar 2020	none	—	—	Details →
1.3.0-rc2	25 Feb 2020	none	—	—	Details →
1.3.0-rc1	19 Feb 2020	none	—	—	Details →
1.2.3	01 Mar 2020	none	—	—	Details →
1.2.2	02 Feb 2020	none	—	—	Details →
1.2.1	28 Jan 2020	none	—	—	Details →
1.2.0	27 Jan 2020	none	—	—	Details →
1.2.0-rc4	18 Jan 2020	none	—	—	Details →
1.2.0-rc3	17 Jan 2020	none	—	—	Details →
1.2.0-rc2	18 Dec 2019	none	—	—	Details →
1.2.0-rc1	24 Nov 2019	none	—	—	Details →
1.1.5	09 Oct 2019	none	—	—	Details →
1.1.4	01 Sep 2019	none	—	—	Details →
1.1.3	20 Aug 2019	none	—	—	Details →
1.1.2	23 Jul 2019	none	—	—	Details →
1.1.1	16 Jul 2019	none	—	—	Details →
1.1.0	10 Jun 2019	none	—	—	Details →
1.1.0-rc3	09 Jun 2019	none	—	—	Details →
1.1.0-rc2	06 Jun 2019	none	—	—	Details →
1.1.0-rc1	06 Jun 2019	none	—	—	Details →
1.0.5	21 Apr 2019	none	—	—	Details →
1.0.4	24 Mar 2019	none	—	—	Details →
1.0.3	07 Mar 2019	none	—	—	Details →
1.0.2	03 Feb 2019	none	—	—	Details →
1.0.1	25 Jan 2019	none	—	—	Details →
1.0.1-rc1	12 Jan 2019	none	—	—	Details →
1.0.0	16 Nov 2018	none	—	—	Details →
1.0.0-rc1	26 Oct 2018	none	—	—	Details →
0.10.2	25 Sep 2018	none	—	—	Details →
0.10.1	16 Sep 2018	none	—	—	Details →
0.10.0	28 Jul 2018	none	—	—	Details →
0.9.3	04 Jun 2018	none	—	—	Details →
0.9.2	19 Apr 2018	none	—	—	Details →
0.9.1	08 Apr 2018	none	—	—	Details →
0.9.0	24 Mar 2018	none	—	—	Details →
0.9.0-rc8	03 Mar 2018	none	—	—	Details →
0.9.0-rc7	24 Feb 2018	none	—	—	Details →
0.9.0-rc6	18 Feb 2018	none	—	—	Details →
0.9.0-rc5	18 Feb 2018	none	—	—	Details →
0.9.0-rc4	18 Feb 2018	none	—	—	Details →
0.9.0-rc3	03 Feb 2018	none	—	—	Details →
0.9.0-rc2	21 Jan 2018	none	—	—	Details →
0.9.0-rc1	07 Jan 2018	none	—	—	Details →
0.8.10	17 Nov 2017	none	—	—	Details →
0.8.9	17 Nov 2017	none	—	—	Details →
0.8.8	08 Oct 2017	none	—	—	Details →
0.8.7	30 Sep 2017	none	—	—	Details →
0.8.6	12 Aug 2017	none	—	—	Details →
0.8.5	08 Aug 2017	none	—	—	Details →
0.8.4	15 Jul 2017	none	—	—	Details →
0.8.3	11 Jul 2017	none	—	—	Details →
0.8.2	06 Jul 2017	none	—	—	Details →
0.8.1	05 Jun 2017	none	—	—	Details →
0.8.0	30 May 2017	none	—	—	Details →
0.8.0-rc7	25 May 2017	none	—	—	Details →
0.8.0-rc6	21 May 2017	none	—	—	Details →
0.8.0-rc5	20 May 2017	none	—	—	Details →
0.8.0-rc4	17 May 2017	none	—	—	Details →
0.8.0-rc3	16 May 2017	none	—	—	Details →
0.8.0-rc2	15 May 2017	none	—	—	Details →
0.8.0-rc1	15 May 2017	none	—	—	Details →
0.7.4	08 May 2017	none	—	—	Details →
0.7.3	14 Apr 2017	none	—	—	Details →

The newest 120 of 187 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for credo

No vulnerabilities match this view.

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 credo

Is credo safe to use?

Vulert has no vulnerabilities on record for credo in Hex at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is credo's Vulert package health score?

Vulert scores credo 96/100, which reads as healthy. 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).

Is the latest version of credo affected?

No. 1.7.19, 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.

How many vulnerabilities does credo have?

0 vulnerabilities are recorded for credo in the Hex ecosystem: 0 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 credo vulnerabilities disclosed?

0 vulnerabilities were recorded for credo in the last 12 months. 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 credo 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 credo for upcoming vulnerabilities?

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