together-ai
The official TypeScript library for the Together API
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/parquetjs | AI (dependencies): Type defs for legitimate parquet lib, low risk. | ai | |
| dependencies | unvetted-dep:@types/progress-stream | AI (dependencies): Type defs for legitimate stream lib, low risk. | ai | |
| phantom-deps | phantom-dep:@types/parquetjs | AI (phantom-deps): TypeScript @types packages are never directly imported; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/progress-stream | AI (phantom-deps): TypeScript @types packages are never directly imported; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node-fetch | AI (phantom-deps): TypeScript @types packages are never directly imported; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript @types packages are never directly imported; phantom-dep is a stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): parquetjs addition is a legitimate dependency for ML dataset support in an AI SDK; no malicious indicators. | ai | |
| dependencies | unvetted-dep:parquetjs | AI (dependencies): parquetjs is a legitimate Apache Parquet library for Node.js; its use in a Together AI SDK for ML dataset uploads is contextually appropriate. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.44.0 | 0 / 0 | |
| 0.43.0 | 0 / 0 | |
| 0.42.0 | 0 / 0 | |
| 0.40.0 | 0 / 0 | |
| 0.39.0 | 0 / 0 | |
| 0.38.0 | 0 / 0 | |
| 0.37.0 | 0 / 0 | |
| 0.33.0 | 0 / 0 | |
| 0.32.0 | 0 / 0 | |
| 0.31.2 | 0 / 0 | |
| 0.31.1 | 0 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.0 | 2 / 0 | |
| 0.29.0 | 2 / 0 | |
| 0.28.0 | 2 / 0 | |
| 0.27.0 | 2 / 0 | |
| 0.26.0 | 2 / 0 | |
| 0.25.0 | 2 / 0 | |
| 0.24.0 | 2 / 0 | |
| 0.23.0 | 2 / 0 | |
| 0.22.0 | 2 / 0 | |
| 0.21.1 | 2 / 0 | |
| 0.21.0 | 2 / 0 | |
| 0.20.0 | 12 / 0 | |
| 0.19.0 | 12 / 0 | |
| 0.18.0 | 12 / 0 | |
| 0.17.0 | 12 / 0 | |
| 0.16.0 | 12 / 0 | |
| 0.15.2 | 12 / 0 | |
| 0.15.1 | 12 / 0 | |
| 0.15.0 | 12 / 0 | |
| 0.14.0 | 12 / 0 | |
| 0.13.0 | 12 / 0 | |
| 0.12.0 | 12 / 0 | |
| 0.11.2 | 12 / 0 | |
| 0.11.1 | 12 / 0 | |
| 0.10.0 | 12 / 0 | |
| 0.9.0 | 12 / 0 | |
| 0.8.0 | 7 / 0 | |
| 0.7.0 | 7 / 0 | |
| 0.6.0 | 7 / 0 | |
| 0.5.2 | 0 / 2 | |
| 0.5.1 | 0 / 2 | |
| 0.5.0 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.0 | 0 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.