spatie/schema-org vulnerabilities
A fluent builder Schema.org types and ld+json generator
- Registry
- Composer
- Latest
- 5.0.2
- License
- MIT
1 known advisory
The latest version, 5.0.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require spatie/schema-org:^5.0.2Is your project on an affected spatie/schema-org?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for spatie/schema-org
Schema.org has cross-site scripting (XSS) via script break-out in toScript() output
- Affected
- >=3.23.1 <3.23.2 · >=4.0.0 <4.0.2
- Fixed in
- 3.23.2, 4.0.2
Is your spatie/schema-org version vulnerable?
- spatie/schema-org 5.0No known advisories in 5.0.2
- spatie/schema-org 4.0No known advisories in 4.0.2
- spatie/schema-org 3.23No known advisories in 3.23.2
- spatie/schema-org 3.22No known advisories in 3.22.0
- spatie/schema-org 3.21No known advisories in 3.21.0
- spatie/schema-org 3.20No known advisories in 3.20.0
- spatie/schema-org 3.19No known advisories in 3.19.0
- spatie/schema-org 3.18No known advisories in 3.18.0
Which of your client projects still run an old spatie/schema-org?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.