Comparison Overview

PyPI

VS

Shopee

PyPI

None
Last Update: 2025-11-28
Between 750 and 799

The Python Package Index (PyPI) is a repository of software for the Python programming language

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 4
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Shopee

5 Science Park Dr, Shopee Building, Singapore, Singapore, SG, 118265
Last Update: 2025-11-28
Between 800 and 849

Shopee is the leading e-commerce platform in Southeast Asia and Taiwan. It is a platform tailored for the region, providing customers with an easy, secure and fast online shopping experience through strong payment and logistical support. Shopee aims to continually enhance its platform and become the region’s e-commerce destination of choice via ongoing product optimisation and localised user-centered strategies. Shopee, a Sea company, was first launched in Singapore in 2015, and has since expanded its reach to Malaysia, Thailand, Taiwan, Indonesia, Vietnam and the Philippines. Sea is a leader in digital entertainment, e-commerce and digital financial services across Greater Southeast Asia. Sea's mission is to better the lives of consumers and small businesses with technology, and is listed on the NYSE under the symbol SE. The Shopee team is rapidly expanding across the region and we are constantly on the lookout for talents who have the passion and drive to become part of a fast-moving and dynamic team. Do check out our career website http://careers.shopee.com for our available positions!

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 55,101
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pypi.jpeg
PyPI
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/shopee.jpeg
Shopee
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
PyPI
100%
Compliance Rate
0/4 Standards Verified
Shopee
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for PyPI in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Shopee in 2025.

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

PyPI cyber incidents detection timeline including parent company and subsidiaries

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

Shopee cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pypi.jpeg
PyPI
Incidents

No Incident

https://images.rankiteo.com/companyimages/shopee.jpeg
Shopee
Incidents

Date Detected: 6/2022
Type:Data Leak
Attack Vector: Phishing emails/messages
Motivation: Financial gain, data theft
Blog: Blog

FAQ

Shopee company demonstrates a stronger AI Cybersecurity Score compared to PyPI company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Shopee company has historically faced a number of disclosed cyber incidents, whereas PyPI company has not reported any.

In the current year, Shopee company and PyPI company have not reported any cyber incidents.

Neither Shopee company nor PyPI company has reported experiencing a ransomware attack publicly.

Neither Shopee company nor PyPI company has reported experiencing a data breach publicly.

Neither Shopee company nor PyPI company has reported experiencing targeted cyberattacks publicly.

Neither PyPI company nor Shopee company has reported experiencing or disclosing vulnerabilities publicly.

Neither PyPI nor Shopee holds any compliance certifications.

Neither company holds any compliance certifications.

Shopee company has more subsidiaries worldwide compared to PyPI company.

Shopee company employs more people globally than PyPI company, reflecting its scale as a Software Development.

Neither PyPI nor Shopee holds SOC 2 Type 1 certification.

Neither PyPI nor Shopee holds SOC 2 Type 2 certification.

Neither PyPI nor Shopee holds ISO 27001 certification.

Neither PyPI nor Shopee holds PCI DSS certification.

Neither PyPI nor Shopee holds HIPAA certification.

Neither PyPI nor Shopee holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.