Is meant-surface-knowledge safe to use?

No. Vulert records a malicious-package vulnerability for meant-surface-knowledge: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is meant-surface-knowledge's Vulert package health score?

Vulert scores meant-surface-knowledge 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of meant-surface-knowledge affected?

Yes. 0.0.1-security.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does meant-surface-knowledge have?

1 vulnerability is recorded for meant-surface-knowledge in the npm ecosystem: 1 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 meant-surface-knowledge vulnerabilities disclosed?

0 vulnerabilities were recorded for meant-surface-knowledge in the last 12 months, and the oldest entry in this database dates to 05 Sep 2025. 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 meant-surface-knowledge 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor meant-surface-knowledge for upcoming vulnerabilities?

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

Vulnerability Database · npm · Package report

meant-surface-knowledge: vulnerability history, versions and safety

meant-surface-knowledge is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded C1

1 with no fix published

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

See the unfixed vulnerabilities →

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all meant-surface-knowledge vulnerabilities

Vulert verdict on meant-surface-knowledge 0.0.1-security.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for meant-surface-knowledge is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100

Security Malicious code published
Maintenance Slowing
Popularity Little adoption
Community Not enough data

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

Current release 0.0.1-security.0 — affected i
Vulnerabilities on record 1 over 1 year · 0 in the last year i
Latest disclosure 05 Sep 2025 i
Highest CVSS n/a i
With no published fix 1 i
Malicious packages 1 i
Last release 30 months ago 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 meant-surface-knowledge, 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
0.0.1-security.0	11 Apr 2024	C1 malicious	—	No	Details →

All 1 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2025 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for meant-surface-knowledge

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Malicious Code Detected in meant-surface-knowledge Package	N/A critical	No fix published	05 Sep 2025

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