@tscircuit/internal-dynamic-import
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Established tscircuit org publisher; 0.0.0 is a common initial version pattern for this ecosystem, not a malware indicator. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.0.13 | 0 / 21 | |
| 0.0.12 | 0 / 21 | |
| 0.0.11 | 0 / 21 | |
| 0.0.10 | 0 / 21 | |
| 0.0.9 | 0 / 21 | |
| 0.0.8 | 0 / 20 | |
| 0.0.7 | 0 / 19 | |
| 0.0.6 | 0 / 19 | |
| 0.0.5 | 0 / 19 | |
| 0.0.4 | 0 / 19 | |
| 0.0.3 | 0 / 19 | |
| 0.0.2 | 0 / 19 | |
| 0.0.0 | 0 / 19 |
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.