@jaypie/datadog
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.12
2 findingsThis version was published by a different npm account than previous versions on 2025-11-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.