← Home

@jaypie/datadog

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

finlaysonstudio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate automation change for this package. ai
publish-pattern new-deps-added AI (publish-pattern): hot-shots is a well-established StatsD client; appropriate dependency for a Datadog metrics package. ai
npm-metadata no-description AI (npm-metadata): Consistently missing description across all versions; cosmetic issue only. ai
bogus-package bogus-package AI (bogus-package): Scoped utility package in an established monorepo; sparse README and missing keywords are not spam indicators here. ai

Versions (showing 24 of 24)

Version Deps Published
1.2.6 2 / 4
1.2.5 2 / 4
1.2.4 2 / 3
1.2.3 2 / 3
1.2.2 2 / 3
1.2.1 2 / 3
1.2.0 2 / 3
1.1.12 4 / 1
1.1.11 4 / 1
1.1.10 4 / 1
1.1.9 3 / 1
1.1.8 3 / 1
1.1.7 3 / 1
1.1.6 3 / 1
1.1.5 3 / 1
1.1.4 3 / 1
1.1.3 3 / 1
1.1.2 3 / 1
1.1.1 3 / 1
1.1.0 3 / 0
1.0.3 3 / 14
1.0.2 3 / 14
1.0.1 3 / 14
1.0.0 3 / 14

v1.2.6

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.

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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