@prosekit/web
A collection of web components for ProseKit
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 | slsa-provenance | AI (provenance): Package has SLSA provenance; stable supply chain signal for this package. | ai | |
| phantom-deps | phantom-dep:@aria-ui/collection | AI (phantom-deps): @aria-ui/collection is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Package uses GitHub Actions CI/CD publishing with SLSA attestation; publisher-changed to GH Actions is expected and stable. | ai | |
| dependencies | unvetted-dep:@aria-ui/overlay | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern. | ai | |
| dependencies | unvetted-dep:@aria-ui/tooltip | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern. | ai | |
| dependencies | unvetted-dep:@aria-ui/presence | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern. | ai | |
| dependencies | unvetted-dep:@aria-ui/popover | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern. | ai | |
| dependencies | unvetted-dep:@aria-ui/menu | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern across prosekit versions. | ai | |
| dependencies | unvetted-dep:@aria-ui/listbox | AI (dependencies): First-party @aria-ui/* UI primitives from same author; stable dependency pattern. | ai | |
| dependencies | unvetted-dep:@prosekit/pm | AI (dependencies): Internal monorepo sibling dep; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@prosekit/extensions | AI (dependencies): Internal monorepo sibling dep; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@prosekit/core | AI (dependencies): Internal monorepo sibling dep; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.8.6 | 9 / 8 | |
| 0.8.5 | 9 / 8 | |
| 0.8.4 | 9 / 8 | |
| 0.8.3 | 9 / 8 | |
| 0.8.2 | 9 / 8 | |
| 0.8.1 | 9 / 8 | |
| 0.8.0 | 9 / 8 | |
| 0.7.13 | 14 / 7 | |
| 0.7.12 | 14 / 7 | |
| 0.7.11 | 14 / 6 | |
| 0.7.10 | 14 / 6 | |
| 0.7.9 | 14 / 6 | |
| 0.7.8 | 14 / 6 | |
| 0.7.7 | 14 / 6 | |
| 0.7.6 | 14 / 6 | |
| 0.7.5 | 14 / 6 | |
| 0.7.4 | 14 / 6 | |
| 0.7.3 | 15 / 6 | |
| 0.7.2 | 15 / 5 | |
| 0.7.1 | 15 / 5 | |
| 0.7.0 | 14 / 5 | |
| 0.6.1 | 14 / 5 | |
| 0.6.0 | 14 / 5 | |
| 0.5.11 | 14 / 5 | |
| 0.5.10 | 14 / 5 | |
| 0.5.9 | 14 / 5 | |
| 0.5.8 | 14 / 5 |
v0.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.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.13
2 findingsThis version was published by a different npm account than previous versions on 2026-03-28. 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.7.12
2 findingsThis version was published by a different npm account than previous versions on 2026-02-22. 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.7.11
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.7.10
2 findingsThis version was published by a different npm account than previous versions on 2026-02-08. 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.7.9
2 findingsThis version was published by a different npm account than previous versions on 2025-12-24. 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.7.8
2 findingsThis version was published by a different npm account than previous versions on 2025-12-08. 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.7.7
2 findingsThis version was published by a different npm account than previous versions on 2025-11-24. 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.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
2 findingsThis version was published by a different npm account than previous versions on 2025-09-09. 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.7.3
2 findingsThis version was published by a different npm account than previous versions on 2025-08-17. 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.7.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-09. 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.7.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-03. 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.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.