@react-pdf/layout
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD publishing with SLSA provenance; expected pattern. | ai | |
| dependencies | unvetted-dep:@react-pdf/fns | AI (dependencies): First-party @react-pdf scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@react-pdf/image | AI (dependencies): First-party @react-pdf scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@react-pdf/types | AI (dependencies): First-party @react-pdf scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@react-pdf/textkit | AI (dependencies): First-party @react-pdf scoped dep from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@react-pdf/stylesheet | AI (dependencies): First-party @react-pdf scoped dep from the same monorepo; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; minimal README and no keywords are expected for internal packages. | ai | |
| phantom-deps | phantom-dep:queue | AI (phantom-deps): queue is declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.6.1 | 9 / 0 | |
| 4.6.0 | 9 / 0 | |
| 4.5.1 | 9 / 0 | |
| 4.5.0 | 9 / 0 | |
| 4.4.3 | 9 / 0 | |
| 4.4.2 | 9 / 0 | |
| 4.4.1 | 9 / 0 |
v4.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.