← Home

@vertz/og

Framework-level Open Graph image generation for Vertz — component to PNG via Satori + resvg

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

viniciusdacal

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): @vertz/og is a scoped OG-image package; Levenshtein match to 'pg' is coincidental. ai
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped OG-image package; no relation to koa. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped OG-image package; no relation to got. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped OG-image package; no relation to qs. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped OG-image package; no relation to joi. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped OG-image package; no relation to zod. ai
phantom-deps phantom-dep:satori AI (phantom-deps): satori is a declared runtime dep; phantom-dep heuristic misfires on bundled ESM output. ai
phantom-deps phantom-dep:@resvg/resvg-js AI (phantom-deps): @resvg/resvg-js is a declared runtime dep; phantom-dep heuristic misfires on bundled ESM output. ai

Versions (showing 3 of 3)

Version Deps Published
0.2.80 2 / 0
0.1.2 2 / 0
0.1.1 2 / 3

v0.2.80

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'pg' typosquat

Package name '@vertz/og' is 1 edit(s) away from popular package 'pg'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.