Vulnerability Database · npm · Package report

ng-table: vulnerability history, versions and safety

Q: How do I monitor ng-table for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the npm 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 ng-table vulnerabilities

Vulert verdict on ng-table 3.0.1 i

Updated on 23 Oct 2026

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

Package health score 54/100

Security Minor issues
Maintenance Unmaintained
Popularity Niche
Community Quiet

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

Current release 3.0.1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 7 packages i
Stars 2,736 i
OpenSSF scorecard 1/10 i
Last release 118 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for ng-table, 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
4.0.0	31 Dec 2016	none	non-standard	—	Details →
3.1.0	31 Dec 2016	none	non-standard	—	Details →
3.0.1	06 Dec 2016	none	non-standard	—	Details →
3.0.0	06 Dec 2016	none	non-standard	—	Details →
2.2.0	27 Nov 2016	none	non-standard	—	Details →
2.1.0	12 Oct 2016	none	non-standard	—	Details →
2.0.2	08 Oct 2016	none	non-standard	—	Details →
2.0.1	08 Oct 2016	none	non-standard	—	Details →
2.0.0	05 Oct 2016	none	non-standard	—	Details →
1.0.0	20 Jun 2016	none	non-standard	—	Details →
0.8.3	19 Apr 2016	none	non-standard	—	Details →
0.5.4	10 Apr 2015	none	non-standard	—	Details →
0.3.2	21 Oct 2014	none	non-standard	—	Details →
0.3.1-npm	28 Apr 2014	none	non-standard	—	Details →
0.3.1	27 Dec 2013	none	non-standard	—	Details →

All 15 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for ng-table

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 ng-table

Is ng-table safe to use?

Vulert has no vulnerabilities on record for ng-table 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 ng-table's Vulert package health score?

Vulert scores ng-table 54/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 ng-table affected?

No. 3.0.1, 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 ng-table should I use?

3.0.1 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 ng-table have?

0 vulnerabilities are recorded for ng-table 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 ng-table vulnerabilities disclosed?

0 vulnerabilities were recorded for ng-table 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 ng-table 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 ng-table for upcoming vulnerabilities?

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