jito-ts
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Declared and used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared and used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/bs58 | AI (phantom-deps): Framework-scoped type package; loaded by convention, stable. | ai | |
| phantom-deps | phantom-dep:rpc-websockets | AI (phantom-deps): Declared and used in config; stable pattern for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 11 / 10 | |
| 4.2.0 | 11 / 10 | |
| 4.1.2 | 11 / 9 | |
| 4.1.1 | 10 / 9 | |
| 4.1.0 | 10 / 9 | |
| 4.0.1 | 8 / 9 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.