@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 51 of 145)
| Version | Deps | Published |
|---|---|---|
| 0.10.32 | 9 / 1 | |
| 0.10.31 | 9 / 1 | |
| 0.10.30 | 9 / 1 | |
| 0.10.29 | 9 / 1 | |
| 0.10.28 | 9 / 1 | |
| 0.10.27 | 9 / 1 | |
| 0.10.26 | 9 / 1 | |
| 0.10.25 | 9 / 1 | |
| 0.10.24 | 9 / 1 | |
| 0.10.23 | 9 / 1 | |
| 0.10.22 | 9 / 1 | |
| 0.10.21 | 9 / 1 | |
| 0.10.20 | 9 / 1 | |
| 0.10.19 | 9 / 1 | |
| 0.10.18 | 9 / 1 | |
| 0.10.17 | 9 / 1 | |
| 0.10.16 | 9 / 1 | |
| 0.10.13 | 9 / 1 | |
| 0.10.11 | 9 / 1 | |
| 0.10.10 | 9 / 1 | |
| 0.10.9 | 9 / 1 | |
| 0.10.8 | 9 / 1 | |
| 0.10.6 | 9 / 1 | |
| 0.10.5 | 9 / 1 | |
| 0.10.3 | 9 / 1 | |
| 0.10.1 | 9 / 1 | |
| 0.9.102 | 9 / 1 | |
| 0.9.101 | 9 / 1 | |
| 0.9.100 | 9 / 1 | |
| 0.9.99 | 9 / 1 | |
| 0.9.98 | 9 / 1 | |
| 0.9.97 | 9 / 1 | |
| 0.9.96 | 9 / 1 | |
| 0.9.95 | 9 / 1 | |
| 0.9.94 | 9 / 1 | |
| 0.9.93 | 9 / 1 | |
| 0.9.92 | 9 / 1 | |
| 0.9.91 | 9 / 1 | |
| 0.9.90 | 9 / 1 | |
| 0.9.89 | 9 / 1 | |
| 0.9.88 | 9 / 1 | |
| 0.9.86 | 9 / 1 | |
| 0.9.85 | 9 / 1 | |
| 0.9.84 | 9 / 1 | |
| 0.9.83 | 9 / 1 | |
| 0.9.82 | 9 / 1 | |
| 0.9.81 | 9 / 1 | |
| 0.9.80 | 9 / 1 | |
| 0.9.79 | 9 / 1 | |
| 0.9.78 | 9 / 1 | |
| 0.9.77 | 9 / 1 |
v0.10.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.16
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.