@git.zone/tspublish
A tool to publish multiple, concise, and small packages from monorepos, specifically for TypeScript projects within a git environment.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist_ts/classes.giteaassets.js | AI (source-diff): Readable compiled TS source, not obfuscation; long-line heuristic false positive. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this publisher's ecosystem; not a meaningful risk signal here. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.11.7 | 11 / 5 | |
| 1.11.6 | 11 / 5 | |
| 1.11.5 | 11 / 5 | |
| 1.11.4 | 11 / 5 | |
| 1.11.3 | 11 / 5 | |
| 1.11.2 | 11 / 5 | |
| 1.11.0 | 11 / 5 | |
| 1.10.3 | 9 / 5 | |
| 1.10.2 | 9 / 5 | |
| 1.10.1 | 9 / 5 | |
| 1.9.1 | 8 / 6 | |
| 1.9.0 | 8 / 6 | |
| 1.7.7 | 7 / 6 | |
| 1.7.6 | 7 / 6 | |
| 1.7.5 | 7 / 6 | |
| 1.7.4 | 7 / 6 | |
| 1.7.3 | 7 / 6 | |
| 1.7.2 | 7 / 6 | |
| 1.6.0 | 7 / 6 | |
| 1.5.5 | 7 / 6 | |
| 1.5.4 | 6 / 6 | |
| 1.5.3 | 6 / 6 | |
| 1.5.2 | 6 / 6 | |
| 1.5.1 | 6 / 6 | |
| 1.5.0 | 6 / 6 | |
| 1.4.0 | 6 / 6 | |
| 1.3.3 | 6 / 6 | |
| 1.3.2 | 6 / 6 | |
| 1.3.1 | 6 / 6 | |
| 1.3.0 | 6 / 6 | |
| 1.2.4 | 6 / 6 | |
| 1.2.3 | 6 / 6 | |
| 1.2.2 | 6 / 6 | |
| 1.2.1 | 6 / 6 | |
| 1.2.0 | 6 / 6 | |
| 1.1.0 | 5 / 6 |
v1.9.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.