@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 — 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 |
|---|---|---|---|---|
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.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: nanashili.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
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.