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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Same legitimate org transition; stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Handoff to gill-maintainers org matches author email/homepage; established over multiple approved versions. | ai | |
| source-diff | obfuscated-file:dist/programs/index.d.ts | AI (source-diff): Generated .d.ts type declarations, long lines from type unions not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/programs/index.d.mts | AI (source-diff): Generated .d.mts type declarations, long lines from type unions not obfuscation. | ai | |
| provenance | missing-githead | AI (provenance): Minor publish hygiene gap for trusted, long-running maintainer; no malicious behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: real, widely-used Solana SDK package, just terse metadata. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Official @solana/* first-party deps matching package's stated Solana SDK purpose. | ai | |
| 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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 8 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.12.0 | 8 / 0 | |
| 0.11.0 | 8 / 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 | |
| 0.8.3 | 8 / 0 | |
| 0.8.2 | 8 / 0 | |
| 0.8.1 | 8 / 0 | |
| 0.8.0 | 8 / 0 | |
| 0.7.0 | 8 / 0 | |
| 0.6.0 | 22 / 0 | |
| 0.5.0 | 22 / 0 | |
| 0.4.0 | 22 / 0 | |
| 0.3.0 | 22 / 0 | |
| 0.2.0 | 22 / 0 | |
| 0.1.0 | 16 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 0 / 0 |
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.8.2
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.8.1
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.8.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.7.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nickfrosty.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.