@goldstack/template-email-send
Utilities for packages that implement email sending using AWS SES
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@goldstack/utils-package-config-embedded | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-cli | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-esbuild | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-org monorepo sibling; stable pattern across all goldstack package versions. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-cli | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-terraform-aws | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Framework-scoped AWS SDK peer dep; loaded by convention, not direct import. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.4.97 | 13 / 11 | |
| 0.4.96 | 13 / 11 | |
| 0.4.95 | 13 / 11 | |
| 0.4.94 | 13 / 11 | |
| 0.4.93 | 13 / 11 | |
| 0.4.90 | 13 / 11 | |
| 0.4.89 | 13 / 11 | |
| 0.4.87 | 13 / 11 | |
| 0.4.86 | 13 / 11 | |
| 0.4.85 | 13 / 11 | |
| 0.4.83 | 13 / 11 | |
| 0.4.82 | 13 / 11 | |
| 0.4.81 | 13 / 11 | |
| 0.4.77 | 13 / 11 | |
| 0.4.72 | 13 / 12 | |
| 0.4.71 | 13 / 12 | |
| 0.4.69 | 13 / 12 | |
| 0.4.68 | 13 / 12 | |
| 0.4.67 | 13 / 12 | |
| 0.4.66 | 13 / 12 | |
| 0.4.65 | 13 / 12 | |
| 0.4.64 | 13 / 12 | |
| 0.4.62 | 13 / 12 | |
| 0.4.61 | 13 / 12 | |
| 0.4.58 | 13 / 12 | |
| 0.4.56 | 13 / 12 |
v0.4.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.