@opentelemetry/instrumentation-lru-memoizer
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): Transition from individual maintainer to GitHub Actions CI/CD; consistent with SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo batch release cadence; dormancy is normal for this OpenTelemetry contrib package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.65.0 | 1 / 3 | |
| 0.64.0 | 1 / 3 | |
| 0.63.0 | 1 / 3 | |
| 0.62.0 | 1 / 3 | |
| 0.61.0 | 1 / 3 | |
| 0.60.0 | 1 / 3 | |
| 0.59.0 | 1 / 3 | |
| 0.58.0 | 1 / 3 | |
| 0.57.0 | 1 / 4 | |
| 0.56.0 | 1 / 4 | |
| 0.55.0 | 1 / 4 | |
| 0.54.0 | 1 / 4 | |
| 0.53.1 | 1 / 4 | |
| 0.53.0 | 1 / 11 | |
| 0.52.0 | 1 / 11 | |
| 0.51.0 | 1 / 11 | |
| 0.50.3 | 1 / 11 | |
| 0.50.2 | 1 / 11 | |
| 0.50.0 | 1 / 11 | |
| 0.49.0 | 1 / 11 | |
| 0.48.0 | 1 / 11 | |
| 0.47.0 | 1 / 11 | |
| 0.46.0 | 1 / 11 | |
| 0.45.0 | 1 / 11 | |
| 0.44.1 | 1 / 11 | |
| 0.44.0 | 1 / 11 | |
| 0.43.0 | 1 / 11 | |
| 0.42.0 | 1 / 11 | |
| 0.41.0 | 1 / 11 | |
| 0.40.0 | 1 / 13 | |
| 0.39.0 | 1 / 13 | |
| 0.38.0 | 1 / 13 | |
| 0.37.0 | 1 / 13 | |
| 0.36.0 | 1 / 13 | |
| 0.35.0 | 1 / 13 | |
| 0.34.0 | 1 / 13 | |
| 0.33.5 | 1 / 13 | |
| 0.33.4 | 1 / 13 | |
| 0.33.3 | 1 / 13 | |
| 0.33.2 | 1 / 13 | |
| 0.33.1 | 1 / 13 | |
| 0.33.0 | 2 / 13 | |
| 0.32.4 | 1 / 13 | |
| 0.32.3 | 1 / 13 | |
| 0.32.2 | 1 / 14 | |
| 0.32.1 | 1 / 14 | |
| 0.32.0 | 1 / 14 | |
| 0.31.0 | 1 / 14 | |
| 0.30.0 | 1 / 14 | |
| 0.29.0 | 1 / 14 |
v0.65.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.64.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.
v0.44.1
1 findingPublished 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 findingPublished 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 findingPublished 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 findingPublished 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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.