Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 1 day ago

PSAdaptiveCards

latest
Top 10k
Set of classes to build AdaptiveCard object
License: unknown
Published: 9 months 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

INCIDENTS FOR THIS VERSION:

Popularity

569
Total Downloads
2
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. Software developers publish components they have authored to public repositories. Some open source repositories allow the developers to take down software component versions that they have published. For open source projects, version unpublishing is uncommon. Versions are typically removed due to a security incident, such as malicious code tampering or accidental development secrets exposure. Software developers often prioritize taking down such packages before informing the community that they have experienced a security incident. Therefore, it is prudent to review the reasons behind software version removals as these events might be a signal of an ongoing software supply chain attack.

Prevalence in PowerShell Gallery community

0 packages
found in
Top 100
1 packages
found in
Top 1k
0 packages
found in
Top 10k
1 packages
in community

Next steps

Review software component documentation for the reasons behind the recent version removal.
If the software version was removed due to a security incident, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

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. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

3 packages
found in
Top 100
9 packages
found in
Top 1k
80 packages
found in
Top 10k
147 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

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. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

8 packages
found in
Top 100
25 packages
found in
Top 1k
130 packages
found in
Top 10k
259 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.

Top behaviors

See all behaviors

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)
97 packages
found in
Top 100
693 packages
found in
Top 1k
4437 packages
found in
Top 10k
7330 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
84 packages
found in
Top 100
284 packages
found in
Top 1k
681 packages
found in
Top 10k
1272 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
1 packages
found in
Top 100
21 packages
found in
Top 1k
130 packages
found in
Top 10k
205 packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
97 packages
found in
Top 100
771 packages
found in
Top 1k
6208 packages
found in
Top 10k
10849 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for PSAdaptiveCards

What is PSAdaptiveCards?

Set of classes to build AdaptiveCard object. For more information about this package, visit its homepage.

Is PSAdaptiveCards malicious or is it safe to use?

The PS Gallery package PSAdaptiveCards 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 PSAdaptiveCards popular?

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

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