@genesislcap/ts-builder
Typescript builder
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@microsoft/api-documenter | AI (dependencies): Well-known Microsoft tooling package; stable false positive for this build-tool package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build tool invoking typescript via config/CLI; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@microsoft/api-extractor | AI (phantom-deps): CLI tool used via config; phantom-dep is expected for this build-tool package. | ai | |
| phantom-deps | phantom-dep:@microsoft/api-documenter | AI (phantom-deps): CLI tool used via config; phantom-dep is expected for this build-tool package. | ai | |
| phantom-deps | phantom-dep:pkg-types | AI (phantom-deps): pkg-types used in config/type resolution context, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@custom-elements-manifest/analyzer | AI (phantom-deps): CEM analyzer is a CLI/config tool, not directly imported; stable false positive for this build tooling package. | ai | |
| phantom-deps | phantom-dep:copyfiles | AI (phantom-deps): copyfiles is a CLI tool used in build scripts, not imported; phantom-dep is a stable false positive for this package. | ai |
Versions (showing 56 of 381)
| Version | Deps | Published |
|---|---|---|
| 14.288.0 | 9 / 1 | |
| 14.287.0 | 9 / 1 | |
| 14.286.0 | 9 / 1 | |
| 14.285.1 | 9 / 1 | |
| 14.285.0 | 9 / 1 | |
| 14.284.5 | 9 / 1 | |
| 14.284.4 | 9 / 1 | |
| 14.284.3 | 9 / 1 | |
| 14.284.2 | 9 / 1 | |
| 14.284.1 | 9 / 1 | |
| 14.284.0 | 9 / 1 | |
| 14.283.2 | 9 / 1 | |
| 14.283.1 | 9 / 1 | |
| 14.283.0 | 9 / 1 | |
| 14.282.0 | 9 / 1 | |
| 14.281.2 | 9 / 1 | |
| 14.281.1 | 9 / 1 | |
| 14.281.0 | 9 / 1 | |
| 14.280.0 | 9 / 1 | |
| 14.278.3 | 9 / 1 | |
| 14.278.2 | 9 / 1 | |
| 14.278.1 | 9 / 1 | |
| 14.278.0 | 9 / 1 | |
| 14.277.0 | 9 / 1 | |
| 14.276.3 | 9 / 1 | |
| 14.276.2 | 9 / 1 | |
| 14.276.1 | 9 / 1 | |
| 14.276.0 | 9 / 1 | |
| 14.275.3 | 9 / 1 | |
| 14.275.2 | 9 / 1 | |
| 14.275.1 | 9 / 1 | |
| 14.275.0 | 9 / 1 | |
| 14.274.1 | 9 / 1 | |
| 14.274.0 | 9 / 1 | |
| 14.273.0 | 9 / 1 | |
| 14.272.0 | 9 / 1 | |
| 14.271.2 | 9 / 1 | |
| 14.271.1 | 9 / 1 | |
| 14.271.0 | 9 / 1 | |
| 14.270.0 | 9 / 1 | |
| 14.269.0 | 9 / 1 | |
| 14.268.4 | 9 / 1 | |
| 14.268.3 | 9 / 1 | |
| 14.268.2 | 9 / 1 | |
| 14.268.1 | 9 / 1 | |
| 14.268.0 | 9 / 1 | |
| 14.267.0 | 9 / 1 | |
| 14.266.1 | 9 / 1 | |
| 14.266.0 | 9 / 1 | |
| 14.265.1 | 9 / 1 | |
| 14.265.0 | 9 / 1 | |
| 14.264.4 | 9 / 1 | |
| 14.264.3 | 9 / 1 | |
| 14.264.2 | 9 / 1 | |
| 14.264.1 | 9 / 1 | |
| 14.264.0 | 9 / 1 |
v14.288.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.287.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.286.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.285.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.285.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.282.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.280.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.277.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.274.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.274.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.273.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.272.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.270.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.269.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.266.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.266.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.265.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.265.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.