@kitschpatrol/aphex
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): dist/aphex-swift is the documented Swift CLI binary for macOS Photos export; darwin/arm64 only, matches package purpose. | ai |
v0.1.2
2 findingsPackage contains compiled binaries that could be backdoors: • dist/aphex-swift
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage contains compiled binaries that could be backdoors: • dist/aphex-swift
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage contains compiled binaries that could be backdoors: • dist/aphex-swift
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.