@sendgrid/mail
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Twilio SendGrid package published by the official twilio-dx account; lack of Sigstore provenance is not a meaningful risk signal for this well-known vendor package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.1.6 | 2 / 0 | |
| 8.1.5 | 2 / 0 | |
| 8.1.4 | 2 / 0 | |
| 8.1.3 | 2 / 0 | |
| 8.1.2 | 2 / 0 | |
| 8.1.1 | 2 / 0 | |
| 8.1.0 | 2 / 0 | |
| 8.0.0 | 2 / 0 |
v8.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.