Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 6 days ago

VSTS

latest
Top 10k
Visual Studio Team Services and Team Foundation Server PowerShell Integration
License: unknown
Published: about 8 years ago
Visit Github
See on PowerShell Gallery

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

Popularity

36.4k
Total Downloads
4
Contributors
0
Declared Dependencies
0
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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in PowerShell Gallery community

100 packages
found in
Top 100
900 packages
found in
Top 1k
8992 packages
found in
Top 10k
17108 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.

Prevalence in PowerShell Gallery community

5 packages
found in
Top 100
126 packages
found in
Top 1k
372 packages
found in
Top 10k
632 packages
in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.
If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

Top behaviors

See all behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
4 packages
found in
Top 100
53 packages
found in
Top 1k
326 packages
found in
Top 10k
512 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
12 packages
found in
Top 100
172 packages
found in
Top 1k
803 packages
found in
Top 10k
1281 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
90 packages
found in
Top 100
509 packages
found in
Top 1k
3113 packages
found in
Top 10k
5185 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6518 packages
found in
Top 10k
11726 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
6 packages
found in
Top 100
142 packages
found in
Top 1k
735 packages
found in
Top 10k
1176 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for VSTS

What is VSTS?

Visual Studio Team Services and Team Foundation Server PowerShell Integration. For more information about this package, visit its homepage.

Is VSTS malicious or is it safe to use?

The PS Gallery package VSTS was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is VSTS popular?

The PS Gallery package VSTS ranks among the top 10000 projects in this community. It has 36K 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 VSTS once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how VSTS behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a VSTS 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.