CommonServiceLocatorv1.3.0

Top 1k

Copy SHA256

License: unknown

Published:

The Common Service Locator library contains a shared interface for service location which application and framework developers can reference. The library provides an abstraction over IoC containers and service locators. Using the library allows an application to indirectly access the capabilities without relying on hard references. The hope is that using this library, third-party applications and frameworks can begin to leverage IoC/Service Location without tying themselves down to a specific implementation.

Warning

Risk: Secrets

1 debugging symbols found

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

1 debugging symbols 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

Issues

See all issues

medium

Detected presence of private debug database files.

secrets

low

Detected digital signatures that have not been performed with an extended validation certificate.

signatures

low

Detected digital signatures that rely on a weak digest algorithm for integrity validation.

signatures

Behaviors

No behaviors found

Vulnerabilities

Downloads

82.74M

Total Downloads

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for CommonServiceLocator

What is CommonServiceLocator?

Is CommonServiceLocator malicious or is it safe to use?

The .NET package CommonServiceLocator 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 downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is CommonServiceLocator popular?

The .NET package CommonServiceLocator ranks among the top 1000 projects in this community. It has 83M 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 CommonServiceLocator once it is in my app?

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