Comparison Overview

Kinsey's

VS

Lamkin Corporation

Kinsey's

1660 Steel Way Drive, Mount Joy, 17543, US
Last Update: 2026-04-04
View Profile
Between 700 and 749
http://www.kinseysinc.com

Founded in 1952, Kinsey’s is a leading distributor to the outdoor and archery industry. Carrying more than 31,000 products from more than 400 vendors, the company offers domestic and international retailers a wide array of products and services including a 1,000-page catalog; an online ordering system; a renowned special order arrow program and more. The company owns innovative consumer brands including October Mountain Products™, Fin-Finder®, BlackHeart™, Elevation® and Alpine™ .

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

Lamkin Corporation

6530 Gateway Park Drive, San Diego, 92154, US
Last Update: 2026-04-04
Between 750 and 799
http://www.lamkingrips.com

Lamkin Corporation, a privately-owned company headquartered in San Diego, is the original manufacturer of premium golf club grips. The company was established in 1925 and initially provided top golf club maker's with leather grips. Over the last 90 years, Lamkin has evolved into the world's leading producer of high-performance golf grips. The most esteemed brands in golf trust Lamkin grips on their premium clubs, along with top Tour players, thousands of PGA professionals and millions of worldwide golfers. Lamkin Grips is dedicated to connecting golfers to a more confident, consistent and enjoyable game.

NAICS: None
NAICS Definition: Others
Employees: 126
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/kinsey's-archery-products.jpeg
Kinsey's
—
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/lamkin-corporation.jpeg
Lamkin Corporation
—
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
Kinsey's
100%
Compliance Rate
0/4 Standards Verified
Lamkin Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Kinsey's in 2026.

Incidents vs Sporting Goods Industry Average (This Year)

No incidents recorded for Lamkin Corporation in 2026.

Incident History — Kinsey's (X = Date, Y = Severity)

Kinsey's cyber incidents detection timeline including parent company and subsidiaries

Incident History — Lamkin Corporation (X = Date, Y = Severity)

Lamkin Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kinsey's-archery-products.jpeg
Kinsey's
Incidents

Date Detected: 1/2025
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/lamkin-corporation.jpeg
Lamkin Corporation
Incidents

No Incident

FAQ

Lamkin Corporation company demonstrates a stronger AI Cybersecurity Score compared to Kinsey's company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Kinsey's company has historically faced a number of disclosed cyber incidents, whereas Lamkin Corporation company has not reported any.

In the current year, Lamkin Corporation company and Kinsey's company have not reported any cyber incidents.

Neither Lamkin Corporation company nor Kinsey's company has reported experiencing a ransomware attack publicly.

Kinsey's company has disclosed at least one data breach, while the other Lamkin Corporation company has not reported such incidents publicly.

Neither Lamkin Corporation company nor Kinsey's company has reported experiencing targeted cyberattacks publicly.

Neither Kinsey's company nor Lamkin Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kinsey's nor Lamkin Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Kinsey's company nor Lamkin Corporation company has publicly disclosed detailed information about the number of their subsidiaries.

Lamkin Corporation company employs more people globally than Kinsey's company, reflecting its scale as a Sporting Goods.

Neither Kinsey's nor Lamkin Corporation holds SOC 2 Type 1 certification.

Neither Kinsey's nor Lamkin Corporation holds SOC 2 Type 2 certification.

Neither Kinsey's nor Lamkin Corporation holds ISO 27001 certification.

Neither Kinsey's nor Lamkin Corporation holds PCI DSS certification.

Neither Kinsey's nor Lamkin Corporation holds HIPAA certification.

Neither Kinsey's nor Lamkin Corporation 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