@scrivr/export-pdf
PDF export for Scrivr documents — same layout pipeline as the canvas renderer
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package is a scoped workspace module in a monorepo; missing repo/keywords and inflated semver are consistent with internal tooling, not spam. | ai | |
| email-domain | unclaimed-email:seraa.ai | AI (email-domain): SLSA provenance attestation provides strong CI/CD identity assurance, partially offsetting the unclaimed domain risk for this package. | ai |
v1.0.10
2 findingsMaintainer email '[email protected]' uses domain 'seraa.ai' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
2 findingsMaintainer email '[email protected]' uses domain 'seraa.ai' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
2 findingsMaintainer email '[email protected]' uses domain 'seraa.ai' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.