@opentelemetry/instrumentation-pg No license 51 versions

@opentelemetry/instrumentation-pg

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

instrumentationnodejsopentelemetrypgpluginpostgrespostgresqlprofilingtracing

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	2026/04/27
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA attestation and org continuity confirm legitimacy.	ai	2026/04/27
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	2026/04/25
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	2026/04/25

Versions (showing 51 of 76)

View all versions

Version	Deps	Published
0.73.0	6 / 6	2026-07-23
0.72.0	6 / 7	2026-07-03
0.71.0	6 / 7	2026-06-11
0.70.0	6 / 7	2026-05-13
0.69.0	6 / 7	2026-05-06
0.68.0	6 / 7	2026-04-29
0.67.0	6 / 7	2026-04-17
0.66.0	6 / 7	2026-03-26
0.65.0	6 / 7	2026-03-04
0.64.0	6 / 7	2026-02-17
0.63.0	6 / 7	2026-01-22
0.62.0	6 / 7	2026-01-15
0.61.2	6 / 7	2025-12-17
0.61.1	6 / 7	2025-11-24
0.61.0	6 / 17	2025-11-06
0.60.0	6 / 17	2025-10-21
0.59.0	6 / 17	2025-10-06
0.58.3	6 / 17	2025-09-29
0.58.2	6 / 17	2025-09-29
0.58.0	6 / 17	2025-09-10
0.57.0	6 / 17	2025-09-08
0.56.1	6 / 17	2025-09-01
0.56.0	6 / 17	2025-08-13
0.55.0	6 / 17	2025-07-09
0.54.1	6 / 17	2025-07-07
0.54.0	6 / 17	2025-06-02
0.53.0	6 / 17	2025-05-15
0.52.0	6 / 17	2025-03-18
0.51.1	6 / 17	2025-02-19
0.51.0	6 / 17	2025-01-28
0.50.0	6 / 17	2024-12-18
0.49.0	6 / 17	2024-12-05
0.48.0	6 / 17	2024-11-18
0.47.1	6 / 17	2024-11-07
0.47.0	6 / 17	2024-10-25
0.46.0	6 / 19	2024-10-16
0.45.1	6 / 19	2024-10-10
0.45.0	5 / 19	2024-10-08
0.44.0	5 / 19	2024-09-02
0.43.0	5 / 19	2024-07-04
0.42.0	5 / 19	2024-06-06
0.41.0	5 / 19	2024-04-25
0.40.0	5 / 19	2024-04-03
0.39.1	5 / 19	2024-03-11
0.39.0	5 / 19	2024-03-06
0.38.0	5 / 19	2024-01-29
0.37.2	6 / 19	2024-01-04
0.37.1	6 / 19	2023-11-22
0.37.0	6 / 19	2023-11-13
0.36.2	6 / 19	2023-10-11
0.36.1	6 / 19	2023-08-14

v0.73.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.72.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.52.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.51.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.51.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.50.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.49.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.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.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.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

LOW No provenance attestation provenance

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

v0.41.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.40.0

1 finding

LOW No provenance attestation provenance

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

v0.39.1

1 finding

LOW No provenance attestation provenance

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

v0.39.0

1 finding

LOW No provenance attestation provenance

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

v0.38.0

1 finding

LOW No provenance attestation provenance

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

v0.37.2

1 finding

LOW No provenance attestation provenance

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

v0.37.1

1 finding

LOW No provenance attestation provenance

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

v0.37.0

1 finding

LOW No provenance attestation provenance

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

v0.36.2

1 finding

LOW No provenance attestation provenance

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

v0.36.1

1 finding

LOW No provenance attestation provenance

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