@plugjs/tsrun
A simple TypeScript runner --------------------------
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance attestation; this is an intentional automation transition, not a compromise. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 1 / 6 | |
| 0.7.1 | 1 / 6 | |
| 0.7.0 | 1 / 6 | |
| 0.6.56 | 1 / 6 | |
| 0.6.55 | 1 / 6 | |
| 0.6.54 | 1 / 6 | |
| 0.6.53 | 1 / 6 | |
| 0.6.52 | 1 / 6 | |
| 0.6.51 | 1 / 6 | |
| 0.6.50 | 1 / 6 | |
| 0.6.49 | 1 / 6 | |
| 0.6.48 | 1 / 6 | |
| 0.6.47 | 1 / 6 | |
| 0.6.46 | 1 / 6 | |
| 0.6.45 | 1 / 6 | |
| 0.6.44 | 1 / 6 | |
| 0.6.43 | 1 / 6 | |
| 0.6.42 | 1 / 6 | |
| 0.6.41 | 1 / 6 | |
| 0.6.40 | 1 / 6 | |
| 0.6.39 | 1 / 6 | |
| 0.6.38 | 1 / 6 | |
| 0.6.37 | 1 / 7 | |
| 0.6.36 | 1 / 7 | |
| 0.6.35 | 1 / 7 | |
| 0.6.34 | 1 / 7 | |
| 0.6.33 | 1 / 7 | |
| 0.6.32 | 1 / 7 | |
| 0.6.31 | 1 / 7 | |
| 0.6.30 | 1 / 7 | |
| 0.6.29 | 1 / 7 | |
| 0.6.28 | 1 / 7 | |
| 0.6.27 | 1 / 7 | |
| 0.6.26 | 1 / 7 | |
| 0.6.25 | 1 / 7 | |
| 0.6.24 | 1 / 7 | |
| 0.6.23 | 1 / 7 | |
| 0.6.22 | 1 / 7 | |
| 0.6.21 | 1 / 7 | |
| 0.6.20 | 1 / 7 | |
| 0.6.19 | 1 / 7 | |
| 0.6.18 | 1 / 7 | |
| 0.6.17 | 1 / 7 | |
| 0.6.16 | 1 / 7 | |
| 0.6.15 | 1 / 7 | |
| 0.6.14 | 1 / 7 | |
| 0.6.13 | 1 / 7 | |
| 0.6.12 | 1 / 7 | |
| 0.6.11 | 1 / 7 | |
| 0.6.10 | 1 / 7 | |
| 0.6.9 | 1 / 7 | |
| 0.6.8 | 1 / 7 | |
| 0.6.7 | 1 / 7 | |
| 0.6.6 | 1 / 7 | |
| 0.6.5 | 1 / 7 | |
| 0.6.4 | 1 / 7 | |
| 0.6.3 | 1 / 7 | |
| 0.6.2 | 1 / 7 | |
| 0.6.1 | 1 / 7 | |
| 0.6.0 | 1 / 7 | |
| 0.5.77 | 1 / 7 | |
| 0.5.76 | 1 / 7 | |
| 0.5.75 | 1 / 7 | |
| 0.5.74 | 1 / 7 | |
| 0.5.73 | 1 / 7 | |
| 0.5.72 | 1 / 7 | |
| 0.5.70 | 1 / 7 | |
| 0.5.69 | 1 / 7 | |
| 0.5.68 | 1 / 7 | |
| 0.5.67 | 1 / 7 | |
| 0.5.66 | 1 / 7 | |
| 0.5.64 | 1 / 7 | |
| 0.5.63 | 1 / 7 | |
| 0.5.62 | 1 / 7 | |
| 0.5.61 | 1 / 7 | |
| 0.5.60 | 1 / 7 | |
| 0.5.59 | 1 / 7 | |
| 0.5.58 | 1 / 7 | |
| 0.5.57 | 1 / 7 | |
| 0.5.56 | 1 / 7 | |
| 0.5.55 | 1 / 7 | |
| 0.5.54 | 1 / 7 | |
| 0.5.53 | 1 / 7 | |
| 0.5.52 | 1 / 7 | |
| 0.5.51 | 1 / 7 | |
| 0.5.50 | 1 / 7 | |
| 0.5.49 | 1 / 7 | |
| 0.5.48 | 1 / 7 | |
| 0.5.47 | 1 / 7 | |
| 0.5.46 | 1 / 7 | |
| 0.5.45 | 1 / 7 | |
| 0.5.44 | 1 / 7 | |
| 0.5.43 | 1 / 7 | |
| 0.5.42 | 1 / 7 | |
| 0.5.41 | 1 / 7 | |
| 0.5.40 | 1 / 7 | |
| 0.5.39 | 1 / 7 | |
| 0.5.38 | 1 / 7 | |
| 0.5.37 | 1 / 7 | |
| 0.5.36 | 1 / 7 |
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.