@opentelemetry/instrumentation-restify
OpenTelemetry instrumentation for `restify` http web application framework
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/restify | AI (dependencies): Types-only dependency from official package. | ai | |
| phantom-deps | phantom-dep:@types/restify | AI (phantom-deps): Type declarations used by convention, not direct import. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing for the OpenTelemetry org; SLSA attested. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.66.0 | 3 / 5 | |
| 0.65.0 | 3 / 6 | |
| 0.64.0 | 3 / 6 | |
| 0.63.0 | 3 / 6 | |
| 0.62.0 | 3 / 6 | |
| 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 / 14 | |
| 0.53.0 | 3 / 14 | |
| 0.52.0 | 3 / 14 | |
| 0.51.2 | 3 / 14 | |
| 0.51.1 | 3 / 14 | |
| 0.51.0 | 3 / 14 | |
| 0.50.0 | 3 / 14 | |
| 0.49.0 | 3 / 14 | |
| 0.48.2 | 3 / 14 | |
| 0.48.1 | 3 / 14 | |
| 0.48.0 | 3 / 14 | |
| 0.47.0 | 3 / 14 | |
| 0.46.0 | 3 / 14 | |
| 0.45.1 | 3 / 14 | |
| 0.45.0 | 3 / 14 | |
| 0.44.0 | 3 / 14 | |
| 0.43.0 | 3 / 14 | |
| 0.42.0 | 3 / 14 | |
| 0.41.0 | 3 / 16 | |
| 0.40.0 | 3 / 16 | |
| 0.39.0 | 3 / 16 | |
| 0.38.0 | 3 / 16 | |
| 0.37.0 | 3 / 16 | |
| 0.36.0 | 3 / 16 | |
| 0.35.0 | 3 / 16 | |
| 0.34.3 | 3 / 16 | |
| 0.34.2 | 3 / 16 | |
| 0.34.1 | 3 / 16 | |
| 0.34.0 | 3 / 16 | |
| 0.33.0 | 4 / 16 | |
| 0.32.4 | 3 / 16 | |
| 0.32.3 | 3 / 16 | |
| 0.32.2 | 3 / 17 | |
| 0.32.1 | 3 / 17 | |
| 0.32.0 | 3 / 17 | |
| 0.31.0 | 3 / 17 | |
| 0.30.1 | 3 / 17 | |
| 0.28.0 | 4 / 13 | |
| 0.25.0 | 4 / 14 |
v0.66.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.46.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.45.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.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.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
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.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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.