@datadog/ai-setup-cli
Interactive tool for Datadog setup
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Declared dependency; used indirectly in config/runtime patterns, not direct imports. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Declared dependency; used indirectly in config/runtime patterns, not direct imports. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Declared dependency; used indirectly in config/runtime patterns, not direct imports. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 15 / 15 | |
| 2.0.11 | 15 / 15 | |
| 2.0.10 | 15 / 15 | |
| 2.0.9 | 15 / 15 | |
| 2.0.8 | 15 / 15 | |
| 2.0.7 | 15 / 15 | |
| 2.0.6 | 15 / 15 | |
| 2.0.5 | 15 / 15 | |
| 2.0.4 | 15 / 15 | |
| 2.0.3 | 15 / 15 | |
| 2.0.2 | 15 / 15 | |
| 2.0.1 | 15 / 15 | |
| 2.0.0 | 15 / 15 | |
| 1.0.12 | 15 / 15 | |
| 1.0.11 | 15 / 15 | |
| 1.0.10 | 15 / 15 | |
| 1.0.9 | 15 / 15 | |
| 1.0.8 | 14 / 15 | |
| 1.0.7 | 14 / 15 | |
| 1.0.6 | 14 / 15 | |
| 1.0.5 | 14 / 15 | |
| 1.0.4 | 14 / 15 | |
| 1.0.3 | 14 / 15 | |
| 1.0.0 | 14 / 15 |
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.