@newrelic/newrelic-capacitor-plugin Apache-2.0 42 versions

@newrelic/newrelic-capacitor-plugin

npm Repository Homepage

NewRelic Plugin for ionic Capacitor

42

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

newrelic

Keywords

capacitorpluginnative

Versions (showing 42 of 42)

Version	Deps	Published
1.6.8	0 / 16	2026-07-02
1.6.7	0 / 16	2026-06-22
1.6.6	0 / 16	2026-05-29
1.6.5	0 / 16	2026-05-21
1.6.4	0 / 16	2026-05-12
1.6.3	0 / 16	2026-04-27
1.6.2	0 / 16	2026-04-07
1.6.1	0 / 16	2026-03-23
1.6.0	0 / 16	2026-03-09
1.5.16	0 / 16	2026-02-13
1.5.15	0 / 16	2026-01-22
1.5.14	0 / 16	2026-01-09
1.5.13	0 / 16	2025-11-14
1.5.12	0 / 16	2025-11-05
1.5.11	0 / 16	2025-10-10
1.5.10	0 / 16	2025-08-13
1.5.9	0 / 16	2025-06-26
1.5.8	0 / 16	2025-05-08
1.5.7	0 / 16	2025-03-31
1.5.6	0 / 16	2025-03-17
1.5.5	0 / 16	2025-02-21
1.5.4	0 / 16	2024-12-10
1.5.3	0 / 16	2024-10-18
1.5.2	0 / 16	2024-09-16
1.5.1	0 / 16	2024-08-21
1.5.0	0 / 16	2024-07-23
1.4.2	0 / 16	2024-07-01
1.4.1	0 / 16	2024-06-03
1.4.0	0 / 16	2024-04-30
1.3.7	0 / 16	2024-03-22
1.3.6	0 / 16	2024-03-05
1.3.5	0 / 16	2024-02-20
1.3.4	0 / 16	2024-02-14
1.3.3	0 / 16	2023-12-20
1.3.2	0 / 16	2023-10-10
1.3.1	0 / 16	2023-08-15
1.3.0	0 / 16	2023-07-18
1.2.1	0 / 16	2023-06-09
1.2.0	0 / 16	2023-05-17
1.1.1	0 / 16	2023-03-24
1.1.0	0 / 16	2023-03-17
1.0.0	0 / 16	2023-01-11

v1.6.8

1 finding

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.

v1.5.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

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.

v1.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

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.

v1.0.0

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.