Vulnerability Database · npm · Package report
@pinecone-database/pinecone: vulnerability history, versions and safety
@pinecone-database/pinecone is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @pinecone-database/pinecone 9.1.0 i
Updated on 23 Oct 2026
Good news: 9.1.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on 9.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 9.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 9.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 2 packages i
- Stars 279 i
- Last release this month i
- Licence Apache-2.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 @pinecone-database/pinecone, 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.
- 9.1.0 20 Oct 2026
- 9.1.0-rc.1.0 08 Oct 2026
- 9.0.0 09 Sep 2026
- 8.2.0 30 Jul 2026
- 8.1.0 21 Jul 2026
- 8.0.0 16 Jun 2026
- 7.2.0 10 Apr 2026
- 7.1.0 19 Feb 2026
- 7.0.0 31 Jan 2026
- 6.1.4 22 Jan 2026
- 6.1.3-dev.20251209000813 09 Dec 2025
- 6.1.3-dev.20251208000834 08 Dec 2025
- 6.1.3-dev.20251207000845 07 Dec 2025
- 6.1.3-dev.20251206000725 06 Dec 2025
- 6.1.3-dev.20251205000825 05 Dec 2025
- 6.1.3-dev.20251204000818 04 Dec 2025
- 6.1.3-dev.20251203000809 03 Dec 2025
- 6.1.3-dev.20251202000824 02 Dec 2025
- 6.1.3-dev.20251201001004 01 Dec 2025
- 6.1.3-dev.20251130000849 30 Nov 2025
- 6.1.3-dev.20251129000737 29 Nov 2025
- 6.1.3-dev.20251128000815 28 Nov 2025
- 6.1.3-dev.20251127000800 27 Nov 2025
- 6.1.3-dev.20251126000800 26 Nov 2025
- 6.1.3-dev.20251125000659 25 Nov 2025
- 6.1.3-dev.20251124000822 24 Nov 2025
- 6.1.3-dev.20251123000849 23 Nov 2025
- 6.1.3-dev.20251122000717 22 Nov 2025
- 6.1.3-dev.20251121000808 21 Nov 2025
- 6.1.3-dev.20251120000738 20 Nov 2025
- 6.1.3-dev.20251119000800 19 Nov 2025
- 6.1.3-dev.20251118000819 18 Nov 2025
- 6.1.3-dev.20251117000814 17 Nov 2025
- 6.1.3-dev.20251116000825 16 Nov 2025
- 6.1.3-dev.20251115000712 15 Nov 2025
- 6.1.3-dev.20251114000740 14 Nov 2025
- 6.1.3-dev.20251113000754 13 Nov 2025
- 6.1.3-dev.20251112000732 12 Nov 2025
- 6.1.3-dev.20251111000746 11 Nov 2025
- 6.1.3-dev.20251110000820 10 Nov 2025
- 6.1.3-dev.20251109000814 09 Nov 2025
- 6.1.3-dev.20251108000706 08 Nov 2025
- 6.1.3-dev.20251107000746 07 Nov 2025
- 6.1.3-dev.20251106000741 06 Nov 2025
- 6.1.3-dev.20251105000739 05 Nov 2025
- 6.1.3-dev.20251104000725 04 Nov 2025
- 6.1.3 03 Nov 2025
- 6.1.2-dev.20251103000825 03 Nov 2025
- 6.1.2-dev.20251102000817 02 Nov 2025
- 6.1.2-dev.20251101000848 01 Nov 2025
- 6.1.2-dev.20251031000718 31 Oct 2025
- 6.1.2-dev.20251030000733 30 Oct 2025
- 6.1.2-dev.20251029000740 29 Oct 2025
- 6.1.2-dev.20251028000710 28 Oct 2025
- 6.1.2-dev.20251027000832 27 Oct 2025
- 6.1.2-dev.20251026000816 26 Oct 2025
- 6.1.2-dev.20251025000712 25 Oct 2025
- 6.1.2-dev.20251024000629 24 Oct 2025
- 6.1.2-dev.20251023000721 23 Oct 2025
- 6.1.2-dev.20251022000724 22 Oct 2025
- 6.1.2-dev.20251020000815 20 Oct 2025
- 6.1.2-dev.20251019000833 19 Oct 2025
- 6.1.2-dev.20251018000648 18 Oct 2025
- 6.1.2-dev.20251017000718 17 Oct 2025
- 6.1.2-dev.20251016000714 16 Oct 2025
- 6.1.2-dev.20251015000709 15 Oct 2025
- 6.1.2-dev.20251014000655 14 Oct 2025
- 6.1.2-dev.20251013000808 13 Oct 2025
- 6.1.2-dev.20251012000756 12 Oct 2025
- 6.1.2-dev.20251011000653 11 Oct 2025
- 6.1.2-dev.20251010000732 10 Oct 2025
- 6.1.2-dev.20251009000654 09 Oct 2025
- 6.1.2-dev.20251008000659 08 Oct 2025
- 6.1.2-dev.20251007000659 07 Oct 2025
- 6.1.2-dev.20251006000740 06 Oct 2025
- 6.1.2-dev.20251005000818 05 Oct 2025
- 6.1.2-dev.20251004000651 04 Oct 2025
- 6.1.2-dev.20251003000640 03 Oct 2025
- 6.1.2-dev.20251002000647 02 Oct 2025
- 6.1.2-dev.20251001000848 01 Oct 2025
- 6.1.2-dev.20250930000721 30 Sep 2025
- 6.1.2-dev.20250929000806 29 Sep 2025
- 6.1.2-dev.20250928000821 28 Sep 2025
- 6.1.2-dev.20250927000704 27 Sep 2025
- 6.1.2-dev.20250926000656 26 Sep 2025
- 6.1.2-dev.20250925000701 25 Sep 2025
- 6.1.2-dev.20250924000710 24 Sep 2025
- 6.1.2-dev.20250923000700 23 Sep 2025
- 6.1.2-dev.20250922000804 22 Sep 2025
- 6.1.2-dev.20250921000813 21 Sep 2025
- 6.1.2-dev.20250920000652 20 Sep 2025
- 6.1.2-dev.20250919000707 19 Sep 2025
- 6.1.2-dev.20250918000658 18 Sep 2025
- 6.1.2-dev.20250917000700 17 Sep 2025
- 6.1.2-dev.20250916000707 16 Sep 2025
- 6.1.2-dev.20250915000815 15 Sep 2025
- 6.1.2-dev.20250914000809 14 Sep 2025
- 6.1.2-dev.20250913000644 13 Sep 2025
- 6.1.2-dev.20250912000657 12 Sep 2025
- 6.1.2-dev.20250911000708 11 Sep 2025
- 6.1.2-dev.20250910000658 10 Sep 2025
- 6.1.2-dev.20250909000721 09 Sep 2025
- 6.1.2-dev.20250907000747 07 Sep 2025
- 6.1.2-dev.20250906000719 06 Sep 2025
- 6.1.2-dev.20250905000741 05 Sep 2025
- 6.1.2-dev.20250904000717 04 Sep 2025
- 6.1.2-dev.20250903000707 03 Sep 2025
- 6.1.2-dev.20250902000736 02 Sep 2025
- 6.1.2-dev.20250901000914 01 Sep 2025
- 6.1.2-dev.20250831000831 31 Aug 2025
- 6.1.2-dev.20250830000655 30 Aug 2025
- 6.1.2-dev.20250829000739 29 Aug 2025
- 6.1.2-dev.20250828000719 28 Aug 2025
- 6.1.2-dev.20250827000743 27 Aug 2025
- 6.1.2-dev.20250826000732 26 Aug 2025
- 6.1.2-dev.20250825000806 25 Aug 2025
- 6.1.2-dev.20250824000826 24 Aug 2025
- 6.1.2-dev.20250823000708 23 Aug 2025
- 6.1.2-dev.20250822000727 22 Aug 2025
- 6.1.2-dev.20250821000641 21 Aug 2025
The newest 120 of 1,066 versions Vulert tracks. 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 @pinecone-database/pinecone
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
Questions
About @pinecone-database/pinecone
Is @pinecone-database/pinecone safe to use?
Vulert has no vulnerabilities on record for @pinecone-database/pinecone 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 @pinecone-database/pinecone's Vulert package health score?
Vulert scores @pinecone-database/pinecone 81/100, which reads as in good shape. 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 @pinecone-database/pinecone affected?
No. 9.1.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.
How many vulnerabilities does @pinecone-database/pinecone have?
0 vulnerabilities are recorded for @pinecone-database/pinecone 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 @pinecone-database/pinecone vulnerabilities disclosed?
0 vulnerabilities were recorded for @pinecone-database/pinecone 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 @pinecone-database/pinecone 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 @pinecone-database/pinecone for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @pinecone-database/pinecone version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.