← Home

pprof-format

npm Repository Homepage
13
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

datadog

Keywords

pprofencodedecodeprofile

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Fires in example.js demo code, not shipped dist output; not a code-exec risk. ai
provenance publisher-changed AI (provenance): Migrated from manual npm publish to GitHub Actions CI/CD with SLSA provenance; expected for Datadog packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer list change consistent with org-level CI/CD migration at Datadog. ai

Versions (showing 13 of 13)

Version Deps Published
2.3.0 0 / 10
2.2.3 0 / 10
2.2.2 0 / 10
2.2.1 0 / 11
2.1.0 0 / 8
2.0.7 0 / 8
2.0.6 0 / 6
2.0.5 0 / 6
2.0.4 0 / 6
2.0.3 0 / 6
2.0.2 0 / 6
2.0.1 0 / 6
2.0.0 0 / 6

v2.3.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.

v2.2.3

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.

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

2 findings
MEDIUM Publisher changed: qard → datadog (on 2023-01-28, unremoved on npm for 1270d) provenance

This version was published by a different npm account (datadog) than the most recent previously approved version (qard) on 2023-01-28. It has since remained available on npm for 1270 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.0.5

2 findings
MEDIUM Publisher changed: qard → datadog (on 2023-01-09, unremoved on npm for 1288d) provenance

This version was published by a different npm account (datadog) than the most recent previously approved version (qard) on 2023-01-09. It has since remained available on npm for 1288 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.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.

v2.0.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.

v2.0.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.