@opentelemetry/instrumentation-pg
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 publishing; SLSA attestation confirms CI provenance. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA attestation and org continuity confirm legitimacy. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): @types/pg is a TypeScript type definition package used for ambient type declarations; not directly imported but legitimately needed as a runtime dependency for type exposure. | ai | |
| phantom-deps | phantom-dep:@types/pg-pool | AI (phantom-deps): @types/pg-pool is a TypeScript type definition package used for ambient type declarations; not directly imported but legitimately needed as a runtime dependency for type exposure. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.73.0 | 6 / 6 | |
| 0.72.0 | 6 / 7 | |
| 0.71.0 | 6 / 7 | |
| 0.70.0 | 6 / 7 | |
| 0.69.0 | 6 / 7 | |
| 0.68.0 | 6 / 7 | |
| 0.67.0 | 6 / 7 | |
| 0.66.0 | 6 / 7 | |
| 0.65.0 | 6 / 7 | |
| 0.64.0 | 6 / 7 | |
| 0.63.0 | 6 / 7 | |
| 0.62.0 | 6 / 7 | |
| 0.61.2 | 6 / 7 | |
| 0.61.1 | 6 / 7 | |
| 0.61.0 | 6 / 17 | |
| 0.60.0 | 6 / 17 | |
| 0.59.0 | 6 / 17 | |
| 0.58.3 | 6 / 17 | |
| 0.58.2 | 6 / 17 | |
| 0.58.0 | 6 / 17 | |
| 0.57.0 | 6 / 17 | |
| 0.56.1 | 6 / 17 | |
| 0.56.0 | 6 / 17 | |
| 0.55.0 | 6 / 17 | |
| 0.54.1 | 6 / 17 | |
| 0.54.0 | 6 / 17 | |
| 0.53.0 | 6 / 17 | |
| 0.52.0 | 6 / 17 | |
| 0.51.1 | 6 / 17 | |
| 0.51.0 | 6 / 17 | |
| 0.50.0 | 6 / 17 | |
| 0.49.0 | 6 / 17 | |
| 0.48.0 | 6 / 17 | |
| 0.47.1 | 6 / 17 | |
| 0.47.0 | 6 / 17 | |
| 0.46.0 | 6 / 19 | |
| 0.45.1 | 6 / 19 | |
| 0.45.0 | 5 / 19 | |
| 0.44.0 | 5 / 19 | |
| 0.43.0 | 5 / 19 | |
| 0.42.0 | 5 / 19 | |
| 0.41.0 | 5 / 19 | |
| 0.40.0 | 5 / 19 | |
| 0.39.1 | 5 / 19 | |
| 0.39.0 | 5 / 19 | |
| 0.38.0 | 5 / 19 | |
| 0.37.2 | 6 / 19 | |
| 0.37.1 | 6 / 19 | |
| 0.37.0 | 6 / 19 | |
| 0.36.2 | 6 / 19 | |
| 0.36.1 | 6 / 19 | |
| 0.36.0 | 7 / 19 | |
| 0.35.3 | 5 / 19 | |
| 0.35.2 | 5 / 19 | |
| 0.35.1 | 5 / 20 | |
| 0.35.0 | 5 / 20 | |
| 0.34.1 | 5 / 20 | |
| 0.34.0 | 5 / 20 | |
| 0.33.0 | 4 / 17 | |
| 0.32.0 | 4 / 17 | |
| 0.31.1 | 4 / 17 | |
| 0.31.0 | 4 / 17 | |
| 0.30.0 | 4 / 17 | |
| 0.29.0 | 4 / 17 | |
| 0.28.0 | 4 / 18 | |
| 0.27.0 | 4 / 18 | |
| 0.26.0 | 4 / 17 | |
| 0.25.0 | 4 / 17 | |
| 0.24.0 | 4 / 17 | |
| 0.23.0 | 4 / 17 | |
| 0.22.0 | 4 / 17 | |
| 0.21.0 | 4 / 17 | |
| 0.20.0 | 5 / 16 | |
| 0.16.0 | 2 / 20 | |
| 0.15.0 | 2 / 21 | |
| 0.14.0 | 2 / 21 |
v0.73.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.72.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.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.51.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.51.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.50.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.49.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.48.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.47.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.47.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.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
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.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
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.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.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.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dyladan) than the most recent previously approved version (obecny) on 2021-04-05, but dyladan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.