Vulnerability Database · Packagist · Package report

reportico-web/reportico: vulnerability history, versions and safety

reportico-web/reportico is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 75 releases, from Nov 2023 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M3
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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.

Vulert verdict on reportico-web/reportico i

Updated on 23 Oct 2026

Careful: 4 of the 4 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 4 vulnerabilities on record across 1 year, none in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2024 i
  • Highest CVSS 6.5 i
  • With no published fix 4 i

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 holds for reportico-web/reportico, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
8.1.0 H1 M2 No Details →
8.0.3 H1 M2 No Details →
8.0.2 H1 M2 No Details →
8.0.1 H1 M2 No Details →
7.1.42-beta H1 M2 No Details →
7.1.41-beta H1 M2 No Details →
7.1.40-beta H1 M2 No Details →
7.1.39-beta H1 M2 No Details →
7.1.38-beta H1 M2 No Details →
7.1.37-beta H1 M2 No Details →
7.1.36-beta H1 M2 No Details →
7.1.35-beta H1 M2 No Details →
7.1.34-beta H1 M2 No Details →
7.1.33-beta H1 M2 No Details →
7.1.32-beta H1 M2 No Details →
7.1.31-beta H1 M2 No Details →
7.1.30-beta H1 M2 No Details →
7.1.29-beta H1 M2 No Details →
7.1.28-beta H1 M2 No Details →
7.1.27-beta H1 M2 No Details →
7.1.26-beta H1 M2 No Details →
7.1.25-beta H1 M2 No Details →
7.1.24-beta H1 M2 No Details →
7.1.23-beta H1 M2 No Details →
7.1.22-beta H1 M2 No Details →
7.1.21-beta H1 M3 No Details →
7.1.20-beta H1 M3 No Details →
7.1.19-beta H1 M3 No Details →
7.1.18-alpha H1 M3 No Details →
7.1.17-alpha H1 M3 No Details →
7.1.16-alpha H1 M3 No Details →
7.1.15-alpha H1 M3 No Details →
7.1.14-alpha H1 M3 No Details →
7.1.13-alpha H1 M3 No Details →
7.1.12-alpha H1 M3 No Details →
7.1.11-alpha H1 M3 No Details →
7.1.10-alpha H1 M3 No Details →
7.1.9-alpha H1 M3 No Details →
7.1.8-alpha H1 M3 No Details →
7.1.7-alpha H1 M3 No Details →
7.1.6-alpha H1 M3 No Details →
7.1.5-alpha H1 M3 No Details →
7.1.4-alpha H1 M3 No Details →
7.1.3-alpha H1 M3 No Details →
7.1.2-alpha H1 M3 No Details →
7.1.1-alpha H1 M3 No Details →
7.1.0-alpha H1 M3 No Details →
7.0.10-alpha H1 M3 No Details →
7.0.9-alpha H1 M3 No Details →
7.0.8-alpha H1 M3 No Details →
7.0.7-alpha H1 M3 No Details →
7.0.6-alpha H1 M3 No Details →
7.0.5-alpha H1 M3 No Details →
7.0.4-alpha H1 M3 No Details →
7.0.3-alpha H1 M3 No Details →
7.0.2-alpha H1 M3 No Details →
7.0.1-alpha H1 M3 No Details →
6.0.16 H1 M3 No Details →
6.0.15 H1 M3 No Details →
6.0.14 H1 M3 No Details →
6.0.13 H1 M3 No Details →
6.0.12 H1 M3 No Details →
6.0.11 H1 M3 No Details →
6.0.10 H1 M3 No Details →
6.0.9 H1 M3 No Details →
6.0.8 H1 M3 No Details →
6.0.7 H1 M3 No Details →
6.0.6 H1 M3 No Details →
6.0.5 H1 M3 No Details →
6.0.4 H1 M3 No Details →
6.0.3 H1 M3 No Details →
6.0.2 H1 M3 No Details →
6.0.1 H1 M3 No Details →
6.0.0 H1 M3 No Details →
4.6 H1 M3 No Details →

Newest 75 of 75 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 3

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

03 Vulnerabilities

Recorded vulnerabilities for reportico-web/reportico

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

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 reportico-web/reportico

Is reportico-web/reportico safe to use?

Vulert records 4 vulnerabilities for reportico-web/reportico in Packagist: 0 critical, 1 high, 3 medium and 0 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does reportico-web/reportico have?

4 vulnerabilities are recorded for reportico-web/reportico in the Packagist ecosystem: 0 critical, 1 high, 3 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 reportico-web/reportico vulnerabilities disclosed?

0 vulnerabilities were recorded for reportico-web/reportico in the last 12 months, and the oldest entry in this database dates to 02 Nov 2023. 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 reportico-web/reportico 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 reportico-web/reportico for upcoming vulnerabilities?

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