← Home

@dynatrace-sdk/client-query

Exposes an API to fetch records stored in Grail.

9
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dynatrace-nodejsstefan.wolfsteiner.dynatracewasserb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Dynatrace SDK org with strong approval history; dormancy consistent with SDK versioning cadence, not takeover indicators. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is same-org @dynatrace-sdk/shared-client-utils replacing @dynatrace-sdk/error-handlers; internal refactor pattern. ai

Versions (showing 9 of 9)

Version Deps Published
1.25.0 2 / 0
1.24.0 2 / 0
1.23.1 2 / 0
1.22.1 2 / 0
1.22.0 2 / 0
1.21.2 2 / 0
1.21.1 3 / 0
1.20.2 3 / 0
1.20.0 3 / 0

v1.25.0

1 finding
LOW No provenance attestation provenance

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

v1.23.1

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.

v1.22.1

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.

v1.22.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.

v1.21.2

1 finding
LOW No provenance attestation provenance

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

v1.21.1

1 finding
LOW No provenance attestation provenance

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

v1.20.2

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.

v1.20.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.