libmime
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): libmime explicitly advertises base64 encoding/decoding as its core functionality; Buffer.from(str, 'base64') is expected and legitimate in this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.4.1 | 4 / 8 | |
| 5.4.0 | 4 / 8 | |
| 5.3.8 | 4 / 8 | |
| 5.3.7 | 4 / 8 | |
| 5.3.6 | 4 / 8 | |
| 5.3.5 | 4 / 8 | |
| 5.3.4 | 4 / 8 | |
| 5.2.1 | 4 / 8 | |
| 5.2.0 | 4 / 8 | |
| 5.1.0 | 4 / 8 | |
| 5.0.0 | 4 / 8 |
v5.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.