Comparison Overview

My Bike Shop

VS

Nokona

My Bike Shop

5965 Exchange Drive, Sykesville, 21784, US
Last Update: 2026-04-04
View Profile
Between 750 and 799
http://www.mybikeshop.com

With roots starting out of the garage of a triathlete in 2012 to having a full warehouse operation - My Bike Shop has has grown rapidly based on a not-so-secret recipe: we hire really, really smart people who are also really, really nice. Most of ‘em also happen to love the sport of cycling too. We’ve amassed some of the brightest minds who know cycling, and more than that…they know cyclists. What binds us together in the MBS family is not two wheels, but what you can do on two wheels. Get it all! Service, price, top notch handling and cashback points - shop at www.mybikeshop.com Follow us on Twitter @ridemybikeshop Follow us on Facebook @ https://www.facebook.com/ridemybikeshop Follow us on Instagram @ https://www.instagram.com/ridemybikeshop/

NAICS: None
NAICS Definition: Others
Employees: 10
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Nokona

4602 E Thomas Rd, Phoenix, 85018, US
Last Update: 2026-04-03
Between 750 and 799
http://nokona.com/

Nokona has been making ballgloves in the USA since 1934, and represents the best of American quality, craftsmanship, and innovation. We are a baseball company, providing top-of-the-line ballgloves and leather goods, all made with our famous, proprietary ballglove leathers. Every Nokona item is individually cut, stamped, stitched, laced, and embroidered by skilled American workers, which gives each one its own unique identity and feel. We are proud to put classic American workmanship into all of our products, using techniques that we have developed and refined for almost 100 years.

NAICS: None
NAICS Definition: Others
Employees: 30
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/my-bike-shop-usa.jpeg
My Bike Shop
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/nokona.jpeg
Nokona
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
My Bike Shop
100%
Compliance Rate
0/4 Standards Verified
Nokona
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for My Bike Shop in 2026.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Nokona in 2026.

Incident History — My Bike Shop (X = Date, Y = Severity)

My Bike Shop cyber incidents detection timeline including parent company and subsidiaries

Incident History — Nokona (X = Date, Y = Severity)

Nokona cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/my-bike-shop-usa.jpeg
My Bike Shop
Incidents

No Incident

https://images.rankiteo.com/companyimages/nokona.jpeg
Nokona
Incidents

No Incident

FAQ

Both My Bike Shop company and Nokona company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Nokona company has disclosed a higher number of cyber incidents compared to My Bike Shop company.

In the current year, Nokona company and My Bike Shop company have not reported any cyber incidents.

Neither Nokona company nor My Bike Shop company has reported experiencing a ransomware attack publicly.

Neither Nokona company nor My Bike Shop company has reported experiencing a data breach publicly.

Neither Nokona company nor My Bike Shop company has reported experiencing targeted cyberattacks publicly.

Neither My Bike Shop company nor Nokona company has reported experiencing or disclosing vulnerabilities publicly.

Neither My Bike Shop nor Nokona holds any compliance certifications.

Neither company holds any compliance certifications.

Neither My Bike Shop company nor Nokona company has publicly disclosed detailed information about the number of their subsidiaries.

Nokona company employs more people globally than My Bike Shop company, reflecting its scale as a Sporting Goods.

Neither My Bike Shop nor Nokona holds SOC 2 Type 1 certification.

Neither My Bike Shop nor Nokona holds SOC 2 Type 2 certification.

Neither My Bike Shop nor Nokona holds ISO 27001 certification.

Neither My Bike Shop nor Nokona holds PCI DSS certification.

Neither My Bike Shop nor Nokona holds HIPAA certification.

Neither My Bike Shop nor Nokona holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References