← Home

@capacitor/haptics

7
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

itschacedionicjsjcesarmobilevmfojpenderdtarnawskymark-ionicalexgerardojacintoos-pedrobilroharvdoggyjpender-osndrkepatotorui.mendesmarkemercapacitor-plugin-boteric-ionicos-ruialves

Keywords

capacitorpluginnative

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migration from capacitor-plugin-bot to GitHub Actions with SLSA provenance is a legitimate CI/CD modernization by the Ionic team. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects Capacitor major version release cadence (v6→v8); package is actively maintained by Ionic team. ai

Versions (showing 7 of 7)

Version Deps Published
8.0.2 0 / 21
8.0.1 0 / 21
8.0.0 0 / 21
7.0.5 0 / 14
7.0.4 0 / 14
7.0.3 0 / 14
6.0.3 0 / 14

v8.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.1

2 findings
HIGH Publisher changed: capacitor-plugin-bot → GitHub Actions (on 2026-02-24) provenance

This version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v8.0.0

2 findings
HIGH Publisher changed: capacitor-plugin-bot → GitHub Actions (on 2025-12-08) provenance

This version was published by a different npm account than previous versions on 2025-12-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.0.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v7.0.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v7.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v6.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.