@tscircuit/soup-util
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Promoting existing first-party peer dep to runtime dep, not a new third-party addition. | ai | |
| dependencies | unvetted-dep:@tscircuit/soup | AI (dependencies): Same-org sibling package from trusted publisher, not third-party unvetted code. | ai | |
| phantom-deps | phantom-dep:@tscircuit/soup | AI (phantom-deps): Same org scope; likely used indirectly, not a real risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Small utility lib naturally has tiny payload/no keywords; publisher is well established. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.0.41 | 1 / 8 | |
| 0.0.40 | 1 / 8 | |
| 0.0.39 | 1 / 8 | |
| 0.0.38 | 1 / 8 | |
| 0.0.37 | 1 / 8 | |
| 0.0.36 | 1 / 8 | |
| 0.0.35 | 1 / 8 | |
| 0.0.34 | 1 / 8 | |
| 0.0.33 | 1 / 8 | |
| 0.0.32 | 1 / 8 | |
| 0.0.31 | 2 / 8 | |
| 0.0.30 | 1 / 9 | |
| 0.0.29 | 1 / 9 | |
| 0.0.28 | 1 / 8 | |
| 0.0.25 | 3 / 6 | |
| 0.0.22 | 2 / 7 | |
| 0.0.20 | 2 / 7 | |
| 0.0.19 | 1 / 8 | |
| 0.0.18 | 1 / 8 | |
| 0.0.17 | 1 / 8 | |
| 0.0.16 | 1 / 8 | |
| 0.0.15 | 1 / 8 | |
| 0.0.14 | 1 / 8 | |
| 0.0.13 | 1 / 8 | |
| 0.0.12 | 0 / 8 | |
| 0.0.11 | 0 / 7 | |
| 0.0.4 | 1 / 6 | |
| 0.0.3 | 0 / 7 | |
| 0.0.2 | 0 / 7 | |
| 0.0.1 | 0 / 7 |
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.