@opentelemetry/instrumentation-memcached
OpenTelemetry instrumentation for `memcached` database client for memcached
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): opentelemetry-js-contrib migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI/CD origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects upstream release cadence, not account takeover; SLSA provenance and official org repo confirm legitimacy. | ai | |
| dependencies | unvetted-dep:@types/memcached | AI (dependencies): @types/memcached is a DefinitelyTyped type-declaration package used for TypeScript type support; it is a stable, benign dependency for this instrumentation package. | ai | |
| phantom-deps | phantom-dep:@types/memcached | AI (phantom-deps): @types/* packages are not directly imported in code; they provide TypeScript type declarations used at compile time. This is expected behavior for this package type. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.61.0 | 3 / 6 | |
| 0.60.0 | 3 / 6 | |
| 0.59.0 | 3 / 6 | |
| 0.58.0 | 3 / 6 | |
| 0.57.0 | 3 / 6 | |
| 0.56.0 | 3 / 6 | |
| 0.55.0 | 3 / 6 | |
| 0.54.0 | 3 / 6 | |
| 0.53.0 | 3 / 6 | |
| 0.52.1 | 3 / 6 | |
| 0.52.0 | 3 / 12 | |
| 0.51.0 | 2 / 13 | |
| 0.50.0 | 2 / 13 | |
| 0.49.3 | 2 / 13 | |
| 0.49.2 | 2 / 13 | |
| 0.49.0 | 3 / 12 | |
| 0.48.0 | 3 / 12 | |
| 0.47.0 | 3 / 12 | |
| 0.46.0 | 3 / 12 | |
| 0.45.0 | 3 / 12 |
v0.61.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.57.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.54.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.51.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.2
2 findingsThis version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.