@code-fixer-23/nx-tsup
An **Nx plugin** for generating and building TypeScript libraries with **[Tsup](https://tsup.egoist.sh/)**.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@nx/devkit | AI (phantom-deps): Referenced in config files; legitimate for Nx plugin packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 1 / 0 | |
| 1.2.4 | 1 / 0 | |
| 1.2.3 | 1 / 0 | |
| 1.2.2 | 4 / 5 | |
| 1.2.1 | 4 / 5 | |
| 1.2.0 | 4 / 5 | |
| 1.1.2 | 4 / 2 | |
| 1.1.0 | 2 / 4 | |
| 1.0.0 | 2 / 4 |
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.