VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@scullyio/scully: vulnerability history, versions and safety

@scullyio/scully is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Apr 2021. 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 H1
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 @scullyio/scully vulnerabilities

Vulert verdict on @scullyio/scully 2.1.41 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.1.41 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 Apr 2021 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 2,528 i
  • OpenSSF scorecard 3/10 i
  • Last release 49 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 @scullyio/scully, 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.1.0-beta.0 19 Jul 2023 none MIT — Details →
2.1.41 21 Sep 2022 none MIT — Details →
2.1.36 13 Jun 2022 none MIT — Details →
2.1.32 20 Apr 2022 none MIT — Details →
2.1.29 28 Mar 2022 none MIT — Details →
2.1.28 25 Mar 2022 none MIT — Details →
2.1.26 15 Mar 2022 none MIT — Details →
2.1.25 12 Mar 2022 none MIT — Details →
3.0.0-beta.1 11 Mar 2022 none MIT — Details →
2.1.24 11 Mar 2022 none MIT — Details →
2.1.21 02 Mar 2022 none MIT — Details →
2.1.20 01 Mar 2022 none MIT — Details →
2.1.19 01 Mar 2022 none MIT — Details →
2.1.18 26 Feb 2022 none MIT — Details →
2.1.16 24 Feb 2022 none MIT — Details →
2.1.14 18 Feb 2022 none MIT — Details →
2.1.13 16 Feb 2022 none MIT — Details →
2.1.12 09 Feb 2022 none MIT — Details →
2.1.11 03 Feb 2022 none MIT — Details →
2.1.10 31 Jan 2022 none MIT — Details →
2.1.9 19 Jan 2022 none MIT — Details →
2.1.8 18 Jan 2022 none MIT — Details →
3.0.0-beta.0 13 Jan 2022 none MIT — Details →
2.1.5 11 Jan 2022 none MIT — Details →
2.1.4 11 Jan 2022 none MIT — Details →
2.1.3 08 Jan 2022 none MIT — Details →
2.1.2 07 Jan 2022 none MIT — Details →
2.1.1 07 Jan 2022 none MIT — Details →
2.1.0 03 Jan 2022 none MIT — Details →
2.1.0-BETA.20211222124715945 22 Dec 2021 none MIT — Details →
2.1.0-BETA.20211221084215284 21 Dec 2021 none MIT — Details →
2.0.3-BETA.124214 17 Dec 2021 none MIT — Details →
2.0.3-BETA.100111 17 Dec 2021 none MIT — Details →
2.0.3-BETA.60859 14 Dec 2021 none MIT — Details →
2.0.3-BETA.161531 13 Dec 2021 none MIT — Details →
2.0.3-BETA.135609 13 Dec 2021 none MIT — Details →
2.0.3-BETA.130515 13 Dec 2021 none MIT — Details →
2.0.3-BETA.123408 13 Dec 2021 none MIT — Details →
2.0.3-BETA.121338 13 Dec 2021 none MIT — Details →
2.0.3-BETA.114714 13 Dec 2021 none MIT — Details →
2.0.3-BETA.113116 13 Dec 2021 none MIT — Details →
2.0.3-BETA.145033 12 Dec 2021 none MIT — Details →
2.0.3-BETA.113624 12 Dec 2021 none MIT — Details →
2.0.3-BETA.112050 12 Dec 2021 none MIT — Details →
2.0.3-BETA.111110 12 Dec 2021 none MIT — Details →
2.0.3-BETA.104118 12 Dec 2021 none MIT — Details →
2.0.3-BETA.134826 11 Dec 2021 none MIT — Details →
2.0.3-BETA.125719 10 Dec 2021 none MIT — Details →
2.0.3-BETA.80452 07 Dec 2021 none MIT — Details →
2.0.3-BETA.102553 03 Dec 2021 none MIT — Details →
2.0.3-BETA.92113 03 Dec 2021 none MIT — Details →
2.0.3-BETA.161855 29 Nov 2021 none MIT — Details →
2.0.3-BETA.153745 29 Nov 2021 none MIT — Details →
2.0.3-BETA.153133 29 Nov 2021 none MIT — Details →
2.0.3-BETA.122159 28 Nov 2021 none MIT — Details →
2.0.3-BETA.192254 27 Nov 2021 none MIT — Details →
2.0.3-BETA.124342 23 Nov 2021 none MIT — Details →
2.0.3-BETA.104022 23 Nov 2021 none MIT — Details →
2.0.3-BETA.103052 23 Nov 2021 none MIT — Details →
2.0.3-BETA.102858 23 Nov 2021 none MIT — Details →
2.0.3-BETA.102507 23 Nov 2021 none MIT — Details →
2.0.3-BETA.144113 22 Nov 2021 none MIT — Details →
2.0.3-BETA.121229 22 Nov 2021 none MIT — Details →
2.0.3-BETA.120227 22 Nov 2021 none MIT — Details →
2.0.3-BETA.120148 22 Nov 2021 none MIT — Details →
2.0.3-BETA.115847 22 Nov 2021 none MIT — Details →
2.0.3-BETA.113332 22 Nov 2021 none MIT — Details →
2.0.3 22 Nov 2021 none MIT — Details →
2.0.2-BETA.102701 22 Nov 2021 none MIT — Details →
2.0.2-BETA.102332 22 Nov 2021 none MIT — Details →
2.0.3-BETA.95849 22 Nov 2021 none MIT — Details →
2.0.2-BETA.84818 21 Nov 2021 none MIT — Details →
2.0.2-BETA.64704 20 Nov 2021 none MIT — Details →
2.0.2-BETA.55609 20 Nov 2021 none MIT — Details →
2.0.2-BETA.143130 19 Nov 2021 none MIT — Details →
2.0.2-BETA.132851 16 Nov 2021 none MIT — Details →
2.0.2-BETA.131106 16 Nov 2021 none MIT — Details →
2.0.2-BETA.130724 16 Nov 2021 none MIT — Details →
2.0.2-BETA.122536 16 Nov 2021 none MIT — Details →
2.0.2-BETA.181935 15 Nov 2021 none MIT — Details →
2.0.2-BETA.133103 15 Nov 2021 none MIT — Details →
2.0.2-BETA.94105 15 Nov 2021 none MIT — Details →
2.0.2-BETA.94902 12 Nov 2021 none MIT — Details →
2.0.2-BETA.92613 12 Nov 2021 none MIT — Details →
2.0.2 12 Nov 2021 none MIT — Details →
2.0.1-BETA.70529 12 Nov 2021 none MIT — Details →
2.0.1-BETA.63423 12 Nov 2021 none MIT — Details →
2.0.1-BETA.33130 12 Nov 2021 none MIT — Details →
2.0.1-BETA.150212 11 Nov 2021 none MIT — Details →
2.0.1-BETA.145311 11 Nov 2021 none MIT — Details →
2.0.1-BETA.143029 11 Nov 2021 none MIT — Details →
2.0.1-BETA.141026 11 Nov 2021 none MIT — Details →
2.0.1-BETA.101943 07 Nov 2021 none MIT — Details →
2.0.1-BETA.145527 06 Nov 2021 none MIT — Details →
2.0.1-BETA.155850 04 Nov 2021 none MIT — Details →
2.0.1-BETA.73219 04 Nov 2021 none MIT — Details →
2.0.1-BETA.144641 01 Nov 2021 none MIT — Details →
2.0.1-BETA.54936 20 Oct 2021 none MIT — Details →
2.0.1-BETA.91017 14 Oct 2021 none MIT — Details →
2.0.1-BETA.62933 14 Oct 2021 none MIT — Details →
2.0.1-BETA.175711 06 Oct 2021 none — — Details →
2.0.1-BETA.72406 06 Oct 2021 none — — Details →
2.0.1 06 Oct 2021 none — — Details →
2.0.0-BETA.152213 05 Oct 2021 none — — Details →
2.0.0-BETA.84430 05 Oct 2021 none — — Details →
2.0.0-BETA.80110 05 Oct 2021 none — — Details →
2.0.0-BETA.165902 04 Oct 2021 none — — Details →
2.0.0-BETA.91342 24 Sep 2021 none — — Details →
2.0.0-BETA.72556 24 Sep 2021 none — — Details →
2.0.0-BETA.71202 24 Sep 2021 none — — Details →
2.0.0-BETA.70300 24 Sep 2021 none — — Details →
2.0.0-BETA.63716 24 Sep 2021 none — — Details →
2.0.0-BETA.60231 24 Sep 2021 none — — Details →
2.0.0-BETA.131856 23 Sep 2021 none — — Details →
2.0.0-BETA.131530 23 Sep 2021 none — — Details →
2.0.0 23 Sep 2021 none — — Details →
1.1.1-BETA.160336 20 Sep 2021 none — — Details →
1.1.1-BETA.124628 20 Sep 2021 none — — Details →
1.1.1-BETA.121023 20 Sep 2021 none — — Details →
1.1.1-BETA.113744 20 Sep 2021 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 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 @scullyio/scully

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-28470: Cross-site Scripting (XSS) in @scullyio/scully 7.3 high 1.0.9 13 Apr 2021

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 @scullyio/scully

Is @scullyio/scully safe to use?

Vulert records 1 vulnerabilities for @scullyio/scully in npm: 0 critical, 1 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 @scullyio/scully's Vulert package health score?

Vulert scores @scullyio/scully 63/100, which reads as usable, but worth attention. 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 @scullyio/scully affected?

No. 2.1.41, 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 @scullyio/scully should I use?

2.1.41 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 @scullyio/scully have?

1 vulnerability is recorded for @scullyio/scully in the npm ecosystem: 0 critical, 1 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 @scullyio/scully vulnerabilities disclosed?

0 vulnerabilities were recorded for @scullyio/scully in the last 12 months, and the oldest entry in this database dates to 13 Apr 2021. 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 @scullyio/scully 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 @scullyio/scully for upcoming vulnerabilities?

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