ts-checker-rspack-plugin
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Standard pattern for spawning worker processes that inherit parent env; core functionality of this type-checker plugin. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is required to run TypeScript type checking in a separate worker process; core functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the user-configured TypeScript installation path in a worker — a standard and expected pattern for a TypeScript checker plugin. Not a security risk. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 4 / 18 | |
| 1.5.0 | 4 / 18 | |
| 1.4.0 | 4 / 18 | |
| 1.3.2 | 4 / 17 | |
| 1.3.1 | 4 / 17 | |
| 1.3.0 | 4 / 16 | |
| 1.2.6 | 7 / 13 | |
| 1.2.5 | 7 / 13 | |
| 1.2.4 | 7 / 13 | |
| 1.2.3 | 7 / 13 | |
| 1.2.2 | 7 / 19 | |
| 1.2.1 | 7 / 19 | |
| 1.2.0 | 7 / 19 | |
| 1.1.7 | 7 / 19 | |
| 1.1.6 | 7 / 19 | |
| 1.1.4 | 7 / 19 | |
| 1.1.3 | 7 / 19 | |
| 1.1.2 | 7 / 19 | |
| 1.1.1 | 6 / 18 | |
| 1.1.0 | 6 / 18 | |
| 1.0.3 | 6 / 18 | |
| 1.0.2 | 6 / 18 | |
| 1.0.1 | 6 / 18 | |
| 1.0.0 | 6 / 18 |
v1.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.