@apollo-deploy/tesseract
Manifest-first SDK generator — turns sdk-manifold/v1 manifests into production-ready TypeScript SDKs
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): 24 versions published in 63 days suggests active iterative development; no malicious indicators accompany the rapid cadence. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): Handlebars is the expected templating engine for this codegen/SDK-generator package; stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fastify-plugin addition aligns with the new ./fastify export; legitimate framework integration. | ai | |
| provenance | no-provenance | AI (provenance): Absence of provenance is common (~88% of npm packages); no other risk signals present. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 7 / 5 | |
| 3.0.0 | 7 / 5 | |
| 2.5.0 | 6 / 5 | |
| 2.4.0 | 6 / 5 | |
| 2.3.0 | 6 / 5 | |
| 2.2.0 | 6 / 5 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.5.0 | 6 / 3 | |
| 0.9.0 | 6 / 3 | |
| 0.8.1 | 6 / 3 | |
| 0.8.0 | 6 / 3 | |
| 0.7.3 | 6 / 3 | |
| 0.7.2 | 6 / 3 | |
| 0.6.0 | 6 / 3 | |
| 0.5.1 | 6 / 3 | |
| 0.5.0 | 6 / 3 | |
| 0.4.4 | 5 / 2 | |
| 0.4.1 | 5 / 2 | |
| 0.1.0 | 5 / 2 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.