Comparison Overview

Root Literary

VS

Melcher Media

Root Literary

Downtown Los Angeles, Los Angeles, California, 90014, US
Last Update: 2025-11-26

Root Literary combines a big-agency business perspective with a boutique hands-on approach to literary representation. Literary agent Holly Root launched over two dozen New York Times bestsellers before founding Root Literary in 2017. The agency's clients benefit from our agents'​ proven skills in identifying talent, negotiating advantageous deals, and advocating for our books all the way from submission to publication. We offer our clients broad-based industry insights as well as individualized strategic thinking to empower each author to define and pursue their own unique path to success. We love what we do, and we do it best in partnership with storytellers who combine artistry with the drive to build a lasting body of work. In short, we’re more than just literary agents—we’re career builders.

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

Melcher Media

124 West 13th Street, New York, NY, 10011, US
Last Update: 2025-11-26
Between 750 and 799

An exceptional story is at the heart of every memorable communication. At Melcher Media, we spend all day, every day, thinking about stories and how to tell them in enduring, authentic, and innovative ways. We get that every story has a distinct voice, vision, message, audience, and objective. And we embrace the fact that we live in a world in which the means of storytelling is changing all the time. In fact, we believe that the vehicle through which a story is presented is integral to the storytelling process. That’s why we don’t confine ourselves to just one medium. From stunning books to interactive apps to websites to films to complex live events and other unique immersive experiences, we’ve been developing and honing award-winning stories for top-notch clients for twenty years.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 14
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/root-literary.jpeg
Root Literary
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/melcher-media.jpeg
Melcher Media
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
Root Literary
100%
Compliance Rate
0/4 Standards Verified
Melcher Media
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Root Literary in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Melcher Media in 2025.

Incident History — Root Literary (X = Date, Y = Severity)

Root Literary cyber incidents detection timeline including parent company and subsidiaries

Incident History — Melcher Media (X = Date, Y = Severity)

Melcher Media cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/root-literary.jpeg
Root Literary
Incidents

No Incident

https://images.rankiteo.com/companyimages/melcher-media.jpeg
Melcher Media
Incidents

No Incident

FAQ

Both Root Literary company and Melcher Media company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Melcher Media company has disclosed a higher number of cyber incidents compared to Root Literary company.

In the current year, Melcher Media company and Root Literary company have not reported any cyber incidents.

Neither Melcher Media company nor Root Literary company has reported experiencing a ransomware attack publicly.

Neither Melcher Media company nor Root Literary company has reported experiencing a data breach publicly.

Neither Melcher Media company nor Root Literary company has reported experiencing targeted cyberattacks publicly.

Neither Root Literary company nor Melcher Media company has reported experiencing or disclosing vulnerabilities publicly.

Neither Root Literary nor Melcher Media holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Root Literary company nor Melcher Media company has publicly disclosed detailed information about the number of their subsidiaries.

Melcher Media company employs more people globally than Root Literary company, reflecting its scale as a Book and Periodical Publishing.

Neither Root Literary nor Melcher Media holds SOC 2 Type 1 certification.

Neither Root Literary nor Melcher Media holds SOC 2 Type 2 certification.

Neither Root Literary nor Melcher Media holds ISO 27001 certification.

Neither Root Literary nor Melcher Media holds PCI DSS certification.

Neither Root Literary nor Melcher Media holds HIPAA certification.

Neither Root Literary nor Melcher Media 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.