@grackle-ai/server
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:@grackle-ai/web | AI (phantom-deps): Same-org monorepo dep; declared as a bundled dependency, not directly imported in this package's code. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Declared and used; config-file reference is legitimate for logging setup. | ai | |
| phantom-deps | phantom-dep:qrcode | AI (phantom-deps): Declared and used; config-file reference is legitimate for QR code generation. | ai | |
| phantom-deps | phantom-dep:@grackle-ai/powerline | AI (phantom-deps): Same-org scoped dependency; legitimate internal package reference. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @grackle-ai/server is not a typosquat of semver; Levenshtein match is a false positive for this package. | ai |
Versions (showing 100 of 200)
| Version | Deps | Published |
|---|---|---|
| 0.112.2 | 21 / 4 | |
| 0.112.1 | 21 / 4 | |
| 0.112.0 | 21 / 4 | |
| 0.111.0 | 21 / 4 | |
| 0.110.3 | 21 / 4 | |
| 0.110.2 | 21 / 4 | |
| 0.110.1 | 21 / 4 | |
| 0.108.4 | 21 / 4 | |
| 0.108.3 | 21 / 4 | |
| 0.108.2 | 21 / 4 | |
| 0.108.1 | 21 / 4 | |
| 0.108.0 | 21 / 4 | |
| 0.107.2 | 21 / 4 | |
| 0.107.1 | 21 / 4 | |
| 0.107.0 | 21 / 4 | |
| 0.106.3 | 21 / 4 | |
| 0.106.2 | 21 / 4 | |
| 0.106.1 | 21 / 4 | |
| 0.106.0 | 21 / 4 | |
| 0.105.0 | 21 / 4 | |
| 0.104.0 | 21 / 4 | |
| 0.103.0 | 21 / 4 | |
| 0.102.0 | 21 / 4 | |
| 0.101.0 | 21 / 4 | |
| 0.100.1 | 21 / 4 | |
| 0.100.0 | 21 / 4 | |
| 0.99.0 | 21 / 4 | |
| 0.98.0 | 20 / 4 | |
| 0.96.3 | 18 / 4 | |
| 0.96.2 | 17 / 4 | |
| 0.96.1 | 17 / 4 | |
| 0.96.0 | 17 / 4 | |
| 0.95.2 | 17 / 4 | |
| 0.95.1 | 16 / 4 | |
| 0.95.0 | 16 / 4 | |
| 0.94.0 | 16 / 4 | |
| 0.93.0 | 16 / 4 | |
| 0.92.3 | 16 / 4 | |
| 0.92.2 | 16 / 4 | |
| 0.92.1 | 16 / 4 | |
| 0.92.0 | 16 / 4 | |
| 0.91.4 | 16 / 4 | |
| 0.91.3 | 16 / 4 | |
| 0.91.2 | 16 / 4 | |
| 0.91.1 | 16 / 4 | |
| 0.91.0 | 16 / 4 | |
| 0.90.0 | 16 / 4 | |
| 0.89.4 | 16 / 4 | |
| 0.89.3 | 16 / 4 | |
| 0.89.2 | 16 / 4 | |
| 0.89.1 | 16 / 4 | |
| 0.89.0 | 16 / 4 | |
| 0.88.0 | 16 / 4 | |
| 0.87.0 | 16 / 4 | |
| 0.86.1 | 16 / 4 | |
| 0.86.0 | 16 / 4 | |
| 0.85.2 | 16 / 4 | |
| 0.85.1 | 16 / 4 | |
| 0.85.0 | 16 / 4 | |
| 0.84.1 | 16 / 4 | |
| 0.84.0 | 16 / 4 | |
| 0.83.2 | 16 / 4 | |
| 0.83.1 | 16 / 4 | |
| 0.83.0 | 16 / 4 | |
| 0.82.2 | 16 / 4 | |
| 0.82.1 | 16 / 4 | |
| 0.82.0 | 16 / 4 | |
| 0.81.0 | 16 / 4 | |
| 0.80.0 | 16 / 4 | |
| 0.79.1 | 16 / 4 | |
| 0.79.0 | 16 / 4 | |
| 0.78.0 | 16 / 4 | |
| 0.77.0 | 16 / 4 | |
| 0.76.3 | 16 / 4 | |
| 0.76.2 | 16 / 4 | |
| 0.76.1 | 16 / 4 | |
| 0.76.0 | 16 / 4 | |
| 0.75.13 | 16 / 4 | |
| 0.75.12 | 16 / 4 | |
| 0.75.11 | 16 / 4 | |
| 0.75.10 | 16 / 4 | |
| 0.75.9 | 16 / 4 | |
| 0.75.8 | 16 / 4 | |
| 0.75.7 | 16 / 4 | |
| 0.75.6 | 16 / 4 | |
| 0.75.5 | 16 / 4 | |
| 0.75.0 | 23 / 7 | |
| 0.74.1 | 23 / 7 | |
| 0.72.6 | 21 / 7 | |
| 0.72.5 | 21 / 7 | |
| 0.72.4 | 21 / 7 | |
| 0.72.3 | 21 / 7 | |
| 0.72.2 | 20 / 7 | |
| 0.72.1 | 16 / 7 | |
| 0.72.0 | 16 / 7 | |
| 0.71.3 | 16 / 7 | |
| 0.71.2 | 16 / 7 | |
| 0.71.1 | 16 / 7 | |
| 0.71.0 | 16 / 7 | |
| 0.70.6 | 16 / 7 |
v0.112.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.112.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.107.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.107.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.106.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.106.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.106.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.106.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.