@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, so a manually published version cannot be tied back to a reviewed commit.
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 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.4.101 | 13 / 11 | |
| 0.4.100 | 13 / 11 | |
| 0.4.99 | 13 / 11 | |
| 0.4.98 | 13 / 11 | |
| 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.84 | 13 / 11 | |
| 0.4.83 | 13 / 11 | |
| 0.4.82 | 13 / 11 | |
| 0.4.81 | 13 / 11 | |
| 0.4.80 | 13 / 11 | |
| 0.4.79 | 13 / 11 | |
| 0.4.77 | 13 / 11 | |
| 0.4.75 | 13 / 12 | |
| 0.4.74 | 13 / 12 | |
| 0.4.73 | 13 / 12 | |
| 0.4.72 | 13 / 12 | |
| 0.4.71 | 13 / 12 | |
| 0.4.70 | 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.63 | 13 / 12 | |
| 0.4.62 | 13 / 12 | |
| 0.4.61 | 13 / 12 | |
| 0.4.60 | 13 / 12 | |
| 0.4.59 | 13 / 12 | |
| 0.4.58 | 13 / 12 | |
| 0.4.57 | 13 / 12 | |
| 0.4.56 | 13 / 12 | |
| 0.4.55 | 13 / 12 | |
| 0.4.54 | 13 / 12 | |
| 0.4.53 | 13 / 12 | |
| 0.4.52 | 13 / 12 | |
| 0.4.51 | 13 / 12 | |
| 0.4.50 | 13 / 12 | |
| 0.4.49 | 13 / 12 | |
| 0.4.48 | 13 / 12 | |
| 0.4.47 | 13 / 12 | |
| 0.4.46 | 13 / 12 | |
| 0.4.45 | 13 / 12 | |
| 0.4.44 | 13 / 12 | |
| 0.4.43 | 13 / 12 | |
| 0.4.42 | 13 / 12 | |
| 0.4.41 | 13 / 12 | |
| 0.4.40 | 13 / 12 | |
| 0.4.39 | 13 / 12 | |
| 0.4.38 | 13 / 12 | |
| 0.4.37 | 13 / 12 | |
| 0.4.36 | 13 / 12 | |
| 0.4.35 | 13 / 12 | |
| 0.4.34 | 13 / 12 | |
| 0.4.33 | 13 / 12 | |
| 0.4.32 | 13 / 12 | |
| 0.4.31 | 13 / 12 | |
| 0.4.30 | 13 / 12 | |
| 0.4.29 | 13 / 12 | |
| 0.4.28 | 13 / 12 | |
| 0.4.27 | 13 / 12 | |
| 0.4.26 | 13 / 12 |
v0.4.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.