← Home

@opentelemetry/instrumentation-ioredis

npm Repository Homepage
51
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dyladanpichlermarcoverbalancenpmjs-accounttrentmmartinkuba

Keywords

instrumentationioredisnodejsopentelemetryprofilingredistracing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@types/ioredis4 AI (dependencies): Type-only alias of well-known @types/ioredis package. ai
publish-pattern new-deps-added AI (publish-pattern): Rename/alias of existing types dep, not a new risk. ai
phantom-deps phantom-dep:@types/ioredis4 AI (phantom-deps): Type-only package, not directly imported by design. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing for the open-telemetry org; expected and stable. ai
publish-pattern dormant-publish AI (publish-pattern): Monorepo release cadence; dormancy reflects package-level gaps, not account inactivity. ai
dependencies unvetted-dep:@opentelemetry/redis-common AI (dependencies): @opentelemetry/redis-common is an official OpenTelemetry package from the same contrib monorepo; it is a legitimate, well-known dependency for Redis instrumentation packages. ai

Versions (showing 51 of 60)

View all versions
Version Deps Published
0.69.0 3 / 6
0.68.0 3 / 7
0.67.0 3 / 7
0.66.0 3 / 7
0.65.0 3 / 7
0.64.0 3 / 7
0.63.0 3 / 7
0.62.0 3 / 7
0.61.0 3 / 7
0.60.0 3 / 7
0.59.0 3 / 7
0.58.0 3 / 7
0.57.0 3 / 7
0.56.0 2 / 17
0.55.0 2 / 17
0.54.0 2 / 17
0.53.3 2 / 17
0.53.2 2 / 17
0.53.0 3 / 16
0.52.0 3 / 16
0.51.0 3 / 16
0.50.1 3 / 16
0.50.0 3 / 16
0.49.0 3 / 16
0.48.0 3 / 16
0.47.1 3 / 16
0.47.0 3 / 16
0.46.0 3 / 16
0.45.0 3 / 16
0.44.0 3 / 16
0.43.0 3 / 18
0.42.0 3 / 18
0.41.0 3 / 18
0.40.0 3 / 18
0.34.2 4 / 17
0.34.1 4 / 18
0.34.0 4 / 18
0.33.2 4 / 18
0.33.1 4 / 18
0.33.0 3 / 18
0.32.2 3 / 18
0.32.1 3 / 18
0.32.0 3 / 18
0.31.0 3 / 18
0.30.0 3 / 18
0.29.0 3 / 18
0.28.0 3 / 18
0.27.1 3 / 19
0.27.0 3 / 17
0.26.0 3 / 17
0.25.0 3 / 17

v0.69.0

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.

v0.68.0

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.

v0.48.0

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.

v0.47.1

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.

v0.47.0

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.

v0.46.0

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.

v0.45.0

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.

v0.44.0

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.

v0.43.0

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.

v0.42.0

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.

v0.41.0

1 finding
LOW No provenance attestation provenance

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

v0.40.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.

v0.34.2

1 finding
LOW No provenance attestation provenance

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

v0.34.1

1 finding
LOW No provenance attestation provenance

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

v0.34.0

1 finding
LOW No provenance attestation provenance

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

v0.33.2

1 finding
LOW No provenance attestation provenance

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

v0.33.1

1 finding
LOW No provenance attestation provenance

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

v0.33.0

1 finding
LOW No provenance attestation provenance

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

v0.32.2

1 finding
LOW No provenance attestation provenance

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

v0.32.1

1 finding
LOW No provenance attestation provenance

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

v0.32.0

1 finding
LOW No provenance attestation provenance

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

v0.31.0

1 finding
LOW No provenance attestation provenance

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

v0.30.0

1 finding
LOW No provenance attestation provenance

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

v0.29.0

1 finding
LOW No provenance attestation provenance

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

v0.28.0

1 finding
LOW No provenance attestation provenance

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

v0.27.1

1 finding
LOW No provenance attestation provenance

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

v0.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

1 finding
LOW No provenance attestation provenance

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