@goldstack/template-email-send-cli MIT 11 versions

@goldstack/template-email-send-cli

npm Repository Homepage

Utilities for packages that implement email sending using AWS SES

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mxro

Keywords

goldstackutilityinfrastructureIaCawsSESemailconfiguration

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Goldstack monorepo consistently publishes without Sigstore provenance; stable pattern across all versions.	ai	2026/05/18
phantom-deps	phantom-dep:source-map-support	AI (phantom-deps): source-map-support is a declared runtime dep used via require at runtime, not directly imported in TS source; stable FP for this package.	ai	2026/05/03
phantom-deps	phantom-dep:@goldstack/template-email-send	AI (phantom-deps): Same-org dep used transitively; phantom-dep FP for this monorepo package.	ai	2026/05/03

Versions (showing 11 of 11)

Version	Deps	Published
0.5.97	8 / 10	2026-05-01
0.5.94	8 / 10	2026-04-16
0.5.87	8 / 10	2026-04-02
0.5.86	8 / 10	2026-03-27
0.5.80	8 / 10	2026-02-02
0.5.79	8 / 10	2026-01-24
0.5.75	8 / 11	2026-01-12
0.5.65	8 / 11	2025-11-25
0.5.62	8 / 11	2025-11-16
0.5.59	8 / 11	2025-09-27
0.5.58	8 / 11	2025-08-05

v0.5.97

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.5.94

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.5.87

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.5.86

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.5.80

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.5.79

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.5.75

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.5.65

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.5.62

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.5.59

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.5.58

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.