sap_extncrepos

@sap/hana-client

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

Please see the "What’s new in the SAP HANA Client" section in the official HANA client 2.18 documentation:

https://help.sap.com/viewer/product/SAP_HANA_CLIENT/2.18/en-US

For the latest updates please see SAP Note 3362072 - SAP HANA Client 2.18 Release Notes

https://launchpad.support.sap.com/#/notes/3362072

 - Issue Number 312829: The poolKey parameter may not have been parsed correctly.

 - Issue Number 313362: An error message involving a getpwuid failure may have been incomplete.

 - Issue Number 310723: SQLDBC could have crashed when working with distributed transactions.

 - Issue Number 301770: Calling status functions on Connection, Statement, or ResultSet objects could have caused the application to block temporarily.

 - Issue Number 310411: The driver could have crashed with a malformed connection string.

 - Issue Number 312275: The Node.js driver included in the HANA Client install for Mac on ARM64 could have failed to install.

 - Issue Number 307786: The client could have crashed when the Transaction Isolation Level was changed.

 - Issue Number 307701: Incorrect results could have been returned after running out of memory.

 - Issue Number 296003: The index server could have exited during out-of-memory situations when SQLDBC tracing was enabled.

 - Issue Number 291672: High CPU usage could have been observed in a multi-threaded SQLDBC application.

 - Issue Number 308137: SQLDBC could have crashed when accessed by a new user or technical user.

Please see the "What’s new in the SAP HANA Client" section in the official HANA client 2.17 documentation:

https://help.sap.com/viewer/product/SAP_HANA_CLIENT/2.17/en-US

For the latest updates please see SAP Note 3329999 - SAP HANA Client 2.17 Release Notes

https://launchpad.support.sap.com/#/notes/3329999

 - Issue Number 310216: Memory used for statement output parameters could have been temporarily higher than necessary.

 - Issue Number 309655: Node.js could have crashed while executing a stored procedure with ST_Geometry out parameters.

 - Issue Number 309136: CCL error "No user exists with SNC name ..." could have occurred.

 - Issue Number 305266: Added missing return type annotation for connect method in index.d.ts.

 - Issue Number 309326: The error "Internal Error: No LOB locator id found for index" could have occurred.

 - Issue Number 309037: SQLDBC could have crashed when the trace file size was limited using the SIZE trace option.

 - Issue Number 305853: Connection.getWarnings could have failed to return warnings.

 - Issue Number 300259: The Node.js driver could have crashed with certain concurrent Statement operations.

 - Issue Number 259321: Pooled connections may not be reused due to session variables.

 - Issue Number 305857: Added reply compression information to PACKET=0 tracing.

 - Issue Number 304108: The client could have returned incorrect CLOB data.

 - Issue Number 303665: Getting VARBINARY column in multiple chunks could have returned incorrect data.

 - Issue Number 300317: Client statement caching may have not reused a cached prepared statement.

 - Issue Number 291233: Getting NVARCHAR column in multiple chunks could have returned incorrect data.

 - Issue Number 288540: There were several issues fetching NCLOB and BLOB values depending on the destination type used.

 - Issue Number 304109: Additional information is now shown in the error message when a network-related exception occurs.

 - Issue Number 282033: Some error messages in SQLDBC-based drivers indicated an issue with a parameter/column value and referenced the parameter/column by number alone.

Please see the "What’s new in the SAP HANA Client" section in the official HANA client 2.16 documentation:

https://help.sap.com/viewer/product/SAP_HANA_CLIENT/2.16/en-US

For the latest updates please see SAP Note 3304880 - SAP HANA Client 2.16 Release Notes

https://launchpad.support.sap.com/#/notes/3304880

 - Issue Number 296115: getParameterValue() could have returned a string value when a numeric value was expected.

 - Issue Number 302885: Statement routed queries could have decreased performance if system replication was enabled.

 - Issue Number 303662: Data fetched from ALPHANUM columns could have been truncated.

 - Issue Number 305945: A spurious -10821 (Session not connected) error could have been traced when a connection was closed.

 - Issue Number 303589: The Node.js driver could have crashed with a "Cannot create a handle without a HandleScope" error.

 - Issue Number 303504: Calling Connection's setAutoCommit and setClientInfo methods leaked a small amount of memory with every invocation.

 - Issue Number 300270: Error text was unclear when mixing implicit and explicit API connection pooling.

      "integrity": "sha512-OX8XqP7/1a9cqkxYw2yXss15f26NKWBpDXQd0/uK/KPqdQhxbPa994hnzjcE2VqQpDslf55723cKPUOGSmMY3g==",

      "integrity": "sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A=="

  "description": "Official SAP HANA Node.js Driver",

  "license": "SEE LICENSE IN developer-license-3_1.txt",

		@@ -9,4 +9,15 @@ # Hana Client 2.18.x Drivers

		https://launchpad.support.sap.com/#/notes/3362072
		https://me.sap.com/notes/3362072

		## Version 2.18.24

		### Changes:

		- Issue Number 312829: The poolKey parameter may not have been parsed correctly.

		### Underlying SQLDBC changes:

		- Issue Number 313362: An error message involving a getpwuid failure may have been incomplete.
		- Issue Number 310723: SQLDBC could have crashed when working with distributed transactions.

		## Version 2.18.22
		@@ -13,0 +24,0 @@

		{
		"name": "@sap/hana-client",
		"version": "2.18.22",
		"version": "2.18.24",
		"lockfileVersion": 1,
		@@ -5,0 +5,0 @@ "requires": true,

		@@ -5,3 +5,3 @@ {
		"description": "Official SAP HANA Node.js Driver",
		"version": "2.18.22",
		"version": "2.18.24",
		"dependencies": {
		@@ -8,0 +8,0 @@ "debug": "3.1.0"

Improved metrics