datagrok-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): Framework dependency loaded by convention in build/API packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:@types/wu | AI (phantom-deps): TypeScript types loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Build tool loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): TypeScript types loaded by convention; stable for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.27.6 | 12 / 18 | |
| 1.27.5 | 12 / 18 | |
| 1.27.4 | 12 / 18 | |
| 1.27.3 | 12 / 18 | |
| 1.27.2 | 12 / 18 | |
| 1.25.7 | 10 / 15 | |
| 1.25.6 | 10 / 15 | |
| 1.25.5 | 10 / 15 | |
| 1.25.4 | 10 / 15 |
v1.27.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.