VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

angular-shepherd: vulnerability history, versions and safety

angular-shepherd is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 angular-shepherd vulnerabilities

Vulert verdict on angular-shepherd 22.0.0 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 22.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 238 i
  • OpenSSF scorecard 3/10 i
  • Last release 8 months ago i
  • Licence AGPL-3.0 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 angular-shepherd, 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
22.0.0 13 Feb 2026 none AGPL-3.0 — Details →
21.0.5 14 Jan 2026 none MIT — Details →
21.0.4 14 Jan 2026 none MIT — Details →
20.0.0 30 Jul 2025 none MIT — Details →
19.0.2 29 Jan 2025 none MIT — Details →
19.0.1 28 Jan 2025 none MIT — Details →
19.0.0 28 Jan 2025 none MIT — Details →
18.0.2 10 Jul 2024 none MIT — Details →
17.0.0 12 Dec 2023 none MIT — Details →
16.0.0 14 Jul 2023 none MIT — Details →
15.0.0 02 Feb 2023 none MIT — Details →
14.0.0 15 Jun 2022 none MIT — Details →
13.0.1 11 Dec 2021 none MIT — Details →
13.0.0 05 Dec 2021 none MIT — Details →
12.0.0 12 Aug 2021 none MIT — Details →
11.0.0 15 Jan 2021 none MIT — Details →
0.7.0 09 Jul 2020 none MIT — Details →
0.6.0 06 Apr 2020 none MIT — Details →
0.5.0 26 Feb 2020 none MIT — Details →
0.4.0 08 Nov 2019 none MIT — Details →
0.3.0 19 Aug 2019 none MIT — Details →
0.2.0 03 Aug 2019 none MIT — Details →
0.1.0 06 Jul 2019 none MIT — Details →
0.0.5 28 May 2019 none MIT — Details →
0.0.4 02 Apr 2019 none MIT — Details →
0.0.3 02 Apr 2019 none MIT — Details →
0.0.2 06 Feb 2019 none MIT — Details →
0.0.1 06 Feb 2019 none MIT — Details →

All 28 versions Vulert tracks for this package. 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.

03 Vulnerabilities

Recorded vulnerabilities for angular-shepherd

No vulnerability write-ups match this view

Search all 0 in the database →

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 angular-shepherd

Is angular-shepherd safe to use?

Vulert has no vulnerabilities on record for angular-shepherd in npm 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 angular-shepherd's Vulert package health score?

Vulert scores angular-shepherd 67/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 angular-shepherd affected?

No. 22.0.0, 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 angular-shepherd should I use?

22.0.0 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 angular-shepherd have?

0 vulnerabilities are recorded for angular-shepherd in the npm 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 angular-shepherd vulnerabilities disclosed?

0 vulnerabilities were recorded for angular-shepherd 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 angular-shepherd 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 angular-shepherd for upcoming vulnerabilities?

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