@polka-codes/runner
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo/internal package; missing repo/homepage/keywords is expected for scoped org packages. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; expected for this org's workflow. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:ignore | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:@polka-codes/core | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:@polka-codes/cli-shared | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/provider | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared dep used in bundled output; phantom-dep heuristic is a false positive for bun-bundled packages. | ai |
Versions (showing 45 of 145)
| Version | Deps | Published |
|---|---|---|
| 0.9.26 | 9 / 2 | |
| 0.9.25 | 9 / 2 | |
| 0.9.24 | 9 / 2 | |
| 0.9.23 | 9 / 2 | |
| 0.9.22 | 9 / 2 | |
| 0.9.21 | 9 / 2 | |
| 0.9.20 | 9 / 2 | |
| 0.9.19 | 9 / 2 | |
| 0.9.18 | 9 / 2 | |
| 0.9.17 | 9 / 2 | |
| 0.9.16 | 9 / 2 | |
| 0.9.15 | 9 / 2 | |
| 0.9.14 | 9 / 2 | |
| 0.9.13 | 9 / 2 | |
| 0.9.12 | 9 / 2 | |
| 0.9.11 | 9 / 2 | |
| 0.9.10 | 9 / 2 | |
| 0.9.9 | 9 / 2 | |
| 0.9.8 | 9 / 2 | |
| 0.9.7 | 9 / 2 | |
| 0.9.6 | 9 / 2 | |
| 0.9.5 | 9 / 2 | |
| 0.9.4 | 9 / 2 | |
| 0.9.3 | 9 / 2 | |
| 0.9.2 | 9 / 2 | |
| 0.9.1 | 9 / 2 | |
| 0.9.0 | 9 / 2 | |
| 0.8.28 | 9 / 2 | |
| 0.8.27 | 9 / 2 | |
| 0.8.26 | 9 / 2 | |
| 0.8.25 | 9 / 2 | |
| 0.8.24 | 9 / 2 | |
| 0.8.23 | 9 / 2 | |
| 0.8.22 | 9 / 2 | |
| 0.8.21 | 9 / 2 | |
| 0.8.20 | 10 / 2 | |
| 0.8.19 | 10 / 2 | |
| 0.8.18 | 10 / 2 | |
| 0.8.17 | 10 / 2 | |
| 0.8.16 | 10 / 2 | |
| 0.8.15 | 10 / 2 | |
| 0.8.14 | 10 / 2 | |
| 0.8.13 | 10 / 2 | |
| 0.8.12 | 10 / 2 | |
| 0.8.11 | 10 / 2 |
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.