emailjs-mime-codec
Encode and decode quoted printable and base64 strings
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is 3760 days old, predating Sigstore provenance. No security concern for this established, well-known package. | ai | |
| source-diff | obfuscated-file:dist/charset.js | AI (source-diff): dist/charset.js is Babel-transpiled ES5 output, not obfuscated malicious code. Long lines are from Babel's iterator/typeof helpers. Stable pattern for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/mimecodec.js | AI (source-diff): dist/mimecodec.js is Babel-transpiled ES5 output exporting standard MIME codec functions. Long lines are Babel artifacts. Stable pattern for this build pipeline. | ai | |
| phantom-deps | phantom-dep:babel-cli | AI (phantom-deps): babel-cli is a build tool used in build scripts, not a runtime import. Correctly flagged as phantom but benign for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode usage is in a unit test file (mimecodec-unit.js) verifying the library's own base64 decoding functionality — expected and benign for a MIME codec package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.9 | 3 / 7 | |
| 2.0.8 | 3 / 7 | |
| 2.0.7 | 3 / 7 | |
| 2.0.6 | 3 / 7 | |
| 2.0.5 | 3 / 7 | |
| 2.0.4 | 3 / 7 | |
| 2.0.3 | 3 / 6 | |
| 2.0.2 | 3 / 7 | |
| 2.0.1 | 3 / 7 | |
| 1.0.3 | 1 / 10 | |
| 1.0.2 | 1 / 10 | |
| 1.0.1 | 1 / 10 | |
| 1.0.0 | 1 / 10 |
v2.0.9
2 findingsThis version was published by a different npm account than previous versions on 2019-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
2 findingsThis version was published by a different npm account than previous versions on 2018-10-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.