@capacitor-community/media
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Scoped @capacitor-community/media has no relation to redis; edit-distance match is a false positive. | ai | |
| email-domain | unclaimed-email:stackspace.ca | AI (email-domain): Stale contributor email; package author and repo match the capacitor-community org with long history. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 9.1.0 | 0 / 16 | |
| 9.0.2 | 0 / 16 | |
| 9.0.1 | 0 / 16 | |
| 9.0.0 | 0 / 16 |
v9.1.0
2 findingsMaintainer email '[email protected]' uses domain 'stackspace.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
2 findingsMaintainer email '[email protected]' uses domain 'stackspace.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
2 findingsMaintainer email '[email protected]' uses domain 'stackspace.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
2 findingsMaintainer email '[email protected]' uses domain 'stackspace.ca' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.