Spectra Assure
Community
Docs
failIncident: Removal
Scanned: 10 days ago

tslib

removed
Top 10
This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.
License: Permissive (ISC)
Published: over 9 years ago
See on npm

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

removal
over 9 years agoReported By: Community

Popularity

44.02B
Recorded Downloads Since 2021
11
Contributors
0
Declared Dependencies
223.46k
Dependents

Top issues

See all issues

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. Developers that use open source components within their applications can specify the exact version of the component their application depends on. However, since components are frequently updated, some developers opt to always use the latest version of the software component. This helps reduce the number of vulnerabilities that open source components can introduce in the application. However, it does expose the developer and the build environment to risks associated with software supply chain attacks. Should a threat actor hijack the ownership of the software component publishing account, or even its publishing token, they could issue a malicious update that can infect the build environment or the application itself. To ensure that the build system updates the software component to a malicious version, threat actors often set the version number to an unusually high value. If a build system is instructed to use the latest component version, it will install the component with the highest version number, and execute its code.

Prevalence in npm community

No prevalence information at this time

Next steps

Review software component versions to ensure there were no accidental code updates.
If the software component versions differ from expected, investigate the build and release environment for software supply chain compromise.
Consider pinning the software component version to prevent accidental code updates.
Avoid using this software package until it is vetted as safe.

Top behaviors

See all behaviors

Prevalence in npm community

No behavior prevalence information at this time

Prevalence in npm community

No behavior prevalence information at this time

Top vulnerabilities

No vulnerabilities found.

FAQ for tslib

What is tslib?

This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it. For more information about this package, visit its homepage.

Is tslib malicious or is it safe to use?

The npm package tslib has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details.

Is tslib popular?

The npm package tslib ranks among the top 10 projects in this community. It has 44B recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure tslib once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how tslib behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a tslib version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.