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

google_places

latest
Top 10k
A Ruby wrapper around the Google Places API.
License: Permissive (MIT)
Published: about 6 years ago
See on RubyGems

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 inactive web service credentials

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

4.77M
Total Downloads
1
Contributor
1
Declared Dependencies
4
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 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

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

16 packages
found in
Top 100
83 packages
found in
Top 1k
671 packages
found in
Top 10k
5227 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.

Problem

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. Web service users can provide a unique key that identifies the caller or confirms the access rights. API keys for supported web services are automatically validated via the least privilege APIs the service exposes. Detected API keys have been refused by their associated service as either inactive or expired. API keys could be considered secret. Keys that can be safely included in a software release package should only be used to identify the caller. For authentication, users should generate their own access keys instead.

Prevalence in RubyGems community

0 packages
found in
Top 100
2 packages
found in
Top 1k
6 packages
found in
Top 10k
29 packages
in community

Next steps

You should securely store web service access keys, and fully automate their management and periodic rotation.
If keys were published unintentionally and the software has been made public, you should revoke exposed keys and file a security incident.

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)
46 packages
found in
Top 100
236 packages
found in
Top 1k
1695 packages
found in
Top 10k
18387 packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
91 packages
found in
Top 100
621 packages
found in
Top 1k
7042 packages
found in
Top 10k
144152 packages
in community

Prevalence in RubyGems community

Behavior often found in this community (Common)
100 packages
found in
Top 100
883 packages
found in
Top 1k
8513 packages
found in
Top 10k
164964 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for google_places

What is google_places?

A Ruby wrapper around the Google Places API. For more information about this package, visit its homepage.

Is google_places malicious or is it safe to use?

The Ruby package google_places 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 google_places popular?

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

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