@grackle-ai/adapter-sdk
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:@bufbuild/protobuf | AI (phantom-deps): Listed as a runtime dep in package.json; likely used transitively or in config/proto files rather than direct JS imports. | ai |
Versions (showing 8 of 208)
| Version | Deps | Published |
|---|---|---|
| 0.40.0 | 4 / 4 | |
| 0.39.1 | 4 / 4 | |
| 0.39.0 | 4 / 4 | |
| 0.38.2 | 4 / 4 | |
| 0.38.1 | 4 / 4 | |
| 0.38.0 | 4 / 4 | |
| 0.37.0 | 4 / 4 | |
| 0.36.0 | 4 / 4 |
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.