Spectra Assure
Community
Docs
warningRisk: Tampering
Scanned: 2 days ago

ceedling

latest
Top 10k
Ceedling is a build automation tool for C unit tests and releases. It's a member of the ThrowTheSwitch.org family of tools. It's built upon Unity and CMock.
License: Permissive (MIT)
Published: 9 months ago
Visit Github
See on RubyGems

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 medium severity vulnerabilities
Hardening
No application hardening issues

Threats

Tampering
1 components with malware history
Malware
No evidence of malware inclusion

INCIDENTS:

Popularity

1.69M
Total Downloads
5
Contributors
6
Declared Dependencies
1
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 projects have a history of security lapses that culminated with a publication of one or more malicious component versions. To ensure that repeated supply chain incidents do not occur, the open source project should be closely monitored for up to two years. All software package versions that are published within two years of the malware incident will convey a warning about the history of security incidents tied to the open source project.

Prevalence in RubyGems community

No prevalence information at this time

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, 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 composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as medium severity.

Prevalence in RubyGems community

37 packages
found in
Top 100
241 packages
found in
Top 1k
3097 packages
found in
Top 10k
47522 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.

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 RubyGems community

No prevalence information at this time

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 composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as low severity.

Prevalence in RubyGems community

11 packages
found in
Top 100
48 packages
found in
Top 1k
550 packages
found in
Top 10k
6318 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
Update the component to the latest version.
Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.

Top behaviors

See all behaviors

Prevalence in RubyGems community

No behavior prevalence information at this time

Prevalence in RubyGems community

Behavior often found in this community (Common)
7 packages
found in
Top 100
33 packages
found in
Top 1k
143 packages
found in
Top 10k
1133 packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
68 packages
found in
Top 100
566 packages
found in
Top 1k
3736 packages
found in
Top 10k
43562 packages
in community

Prevalence in RubyGems community

Behavior uncommon for this community (Uncommon)
2 packages
found in
Top 100
7 packages
found in
Top 1k
50 packages
found in
Top 10k
293 packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
45 packages
found in
Top 100
186 packages
found in
Top 1k
1704 packages
found in
Top 10k
18027 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
1 (1 Fixable)
CVE-2025-54314l
1 (1 Fixable)
CVE-2020-8130m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for ceedling

What is ceedling?

Ceedling is a build automation tool for C unit tests and releases. It's a member of the ThrowTheSwitch.org family of tools. It's built upon Unity and CMock. For more information about this package, visit its homepage.

Is ceedling malicious or is it safe to use?

The Ruby package ceedling was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 1 other issue and risky behavior was found. 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. The package ceedling had 1 incidents in versions published within 2 years prior to the latest.

Is ceedling popular?

The Ruby package ceedling ranks among the top 10000 projects in this community. It has 2M 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 ceedling once it is in my app?

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