resend
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): Generated .d.cts type declarations (tsdown --dts); long lines are union types, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Legit manual→CI/CD transition with SLSA attestation on canonical Resend SDK. | ai | |
| provenance | missing-githead | AI (provenance): Expected side-effect of moving to CI/CD attested publish. | ai | |
| dependencies | unvetted-dep:svix | AI (dependencies): svix is a well-known webhook verification SDK; its use in resend is expected and legitimate. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 6.18.0 | 2 / 18 | |
| 6.17.2 | 2 / 18 | |
| 6.17.1 | 2 / 18 | |
| 6.17.0 | 2 / 17 | |
| 6.16.0 | 2 / 17 | |
| 6.15.0 | 2 / 17 | |
| 6.14.0 | 2 / 17 | |
| 6.13.0 | 2 / 17 | |
| 6.12.4 | 2 / 17 | |
| 6.12.3 | 2 / 17 | |
| 6.12.2 | 2 / 17 | |
| 6.12.1 | 2 / 17 | |
| 6.12.0 | 2 / 17 | |
| 6.11.0 | 2 / 17 | |
| 6.10.0 | 2 / 17 | |
| 6.9.4 | 2 / 17 | |
| 6.9.3 | 2 / 17 | |
| 6.9.2 | 2 / 17 | |
| 6.9.1 | 2 / 17 | |
| 6.9.0 | 2 / 15 | |
| 6.8.0 | 1 / 14 | |
| 6.7.0 | 1 / 14 | |
| 6.6.0 | 1 / 14 | |
| 6.5.2 | 1 / 14 | |
| 6.5.1 | 1 / 14 | |
| 6.5.0 | 1 / 14 | |
| 6.4.2 | 1 / 14 | |
| 6.4.1 | 1 / 14 | |
| 6.4.0 | 1 / 14 | |
| 6.3.0 | 1 / 8 | |
| 6.2.2 | 1 / 8 | |
| 6.2.1 | 1 / 8 | |
| 6.2.0 | 1 / 8 | |
| 6.1.3 | 0 / 8 | |
| 6.1.2 | 0 / 8 | |
| 6.1.1 | 0 / 8 | |
| 6.1.0 | 0 / 8 | |
| 6.0.3 | 0 / 10 | |
| 6.0.2 | 0 / 10 | |
| 6.0.1 | 0 / 10 | |
| 6.0.0 | 0 / 10 |
v6.18.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v6.17.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.17.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.17.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (lucasfcosta) on 2026-07-03, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.12.3
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (carolina-josephik) on 2026-05-06, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jopcmelo) than the most recent previously approved version (cisneiros) on 2026-03-16, but jopcmelo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2026-02-27, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2026-02-10, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2026-01-27, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2026-01-27, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.8.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2026-01-19, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vcapretz) than the most recent previously approved version (cisneiros) on 2026-01-08, but vcapretz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lucasfcosta) than the most recent previously approved version (cisneiros) on 2025-12-09, but lucasfcosta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.5.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2025-11-19, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.5.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gabrielmfern.
This version was published by a different npm account (gabrielmfern) than the most recent previously approved version (cisneiros) on 2025-11-19, but gabrielmfern is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lucasfcosta) than the most recent previously approved version (cisneiros) on 2025-11-18, but lucasfcosta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.