gill
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/programs/token/reexports.d.ts | AI (source-diff): Auto-generated .d.ts barrel re-export file; long lines are expected for large Solana token program symbol lists. | ai | |
| dependencies | unvetted-dep:@solana-program/address-lookup-table | AI (dependencies): Legitimate Solana ecosystem package; stable dependency for this Solana client library. | ai | |
| phantom-deps | phantom-dep:@gillsdk/config-eslint | AI (phantom-deps): Internal ESLint config accidentally in dependencies; not a runtime import, stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 8 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.10.3 | 8 / 0 | |
| 0.10.2 | 8 / 0 | |
| 0.10.1 | 8 / 0 | |
| 0.10.0 | 8 / 0 | |
| 0.9.2 | 8 / 0 | |
| 0.9.1 | 8 / 0 | |
| 0.9.0 | 8 / 0 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.