exifr
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): exifr is an EXIF reader that legitimately decodes base64-encoded image data. This is core library functionality, not a malicious payload pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard CJS/ESM compatibility shim for optional dependency loading. The module name is library-controlled, not user-controlled. Stable pattern for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.1.3 | 0 / 30 | |
| 7.1.2 | 0 / 30 | |
| 7.1.1 | 0 / 30 | |
| 7.1.0 | 0 / 30 | |
| 7.0.0 | 0 / 30 |
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.