← Home

@better-svelte-email/cli

npm Repository

CLI for better-svelte-email

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

konixy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): resend is a legitimate email-sending SDK; addition is consistent with this email CLI tool's purpose. ai
provenance no-provenance AI (provenance): Small OSS monorepo CLI; no CI provenance is common at this scale and poses low risk given clean code signals. ai
phantom-deps phantom-dep:@sveltejs/kit AI (phantom-deps): Framework-scoped package loaded by convention; stable FP. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @better-svelte-email/cli has no relation to joi; edit-distance match is spurious. ai
phantom-deps phantom-dep:@better-svelte-email/preview-server AI (phantom-deps): Same-org sibling; orchestrated at runtime by CLI; stable FP. ai
phantom-deps phantom-dep:@better-svelte-email/server AI (phantom-deps): Same-org sibling package used at runtime via preview-server; stable FP. ai
phantom-deps phantom-dep:svelte AI (phantom-deps): Svelte is a framework peer dep referenced in config; stable FP. ai

Versions (showing 3 of 3)

Version Deps Published
2.1.0 10 / 0
2.0.1 9 / 0
2.0.0 9 / 0

v2.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

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.