@contractspec/lib.presentation-runtime-react
React presentation runtime with workflow components
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser/table.state.js | AI (source-diff): Bun-bundled minified output with readable logic and same-org imports; stable build artifact pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/table.state.js | AI (source-diff): // @bun header confirms standard Bun bundler output; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.ui-kit-web | AI (phantom-deps): Same-org dependency declared in package.json; likely used transitively or in type declarations. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 40.0.3 | 4 / 2 | |
| 40.0.2 | 4 / 2 | |
| 40.0.1 | 4 / 2 | |
| 40.0.0 | 4 / 2 | |
| 39.0.1 | 4 / 2 | |
| 39.0.0 | 4 / 2 | |
| 38.0.3 | 4 / 2 | |
| 38.0.2 | 4 / 2 | |
| 38.0.1 | 4 / 2 | |
| 38.0.0 | 4 / 2 | |
| 36.0.8 | 4 / 2 | |
| 36.0.7 | 4 / 2 | |
| 36.0.6 | 4 / 2 | |
| 36.0.5 | 4 / 2 | |
| 36.0.4 | 4 / 2 | |
| 36.0.3 | 4 / 2 | |
| 36.0.2 | 4 / 2 | |
| 36.0.0 | 4 / 2 | |
| 35.0.3 | 4 / 2 | |
| 35.0.0 | 4 / 2 | |
| 34.0.6 | 4 / 2 | |
| 34.0.5 | 4 / 2 | |
| 34.0.4 | 4 / 2 | |
| 34.0.3 | 4 / 2 | |
| 34.0.1 | 4 / 2 | |
| 34.0.0 | 4 / 2 | |
| 33.0.0 | 4 / 2 | |
| 32.0.5 | 4 / 2 | |
| 32.0.4 | 4 / 2 | |
| 32.0.3 | 4 / 2 | |
| 32.0.2 | 4 / 2 | |
| 32.0.0 | 4 / 2 | |
| 31.0.3 | 4 / 2 | |
| 31.0.2 | 4 / 2 | |
| 31.0.1 | 4 / 2 | |
| 31.0.0 | 4 / 2 | |
| 30.0.0 | 4 / 2 | |
| 29.0.0 | 4 / 2 | |
| 28.0.1 | 4 / 2 | |
| 27.0.0 | 4 / 2 | |
| 26.0.1 | 4 / 2 | |
| 26.0.0 | 4 / 2 | |
| 25.0.0 | 4 / 2 | |
| 24.0.0 | 4 / 2 | |
| 23.0.1 | 4 / 2 | |
| 23.0.0 | 4 / 2 | |
| 22.0.0 | 4 / 2 | |
| 21.0.0 | 4 / 2 | |
| 20.0.0 | 4 / 2 | |
| 19.0.0 | 4 / 2 | |
| 18.0.1 | 4 / 2 | |
| 18.0.0 | 4 / 2 | |
| 17.0.0 | 4 / 2 | |
| 16.0.0 | 4 / 2 | |
| 15.0.0 | 4 / 2 | |
| 14.0.0 | 4 / 2 | |
| 13.0.0 | 4 / 2 | |
| 12.0.0 | 4 / 2 | |
| 11.0.0 | 4 / 1 | |
| 10.0.1 | 4 / 1 | |
| 10.0.0 | 4 / 1 | |
| 9.0.0 | 4 / 1 | |
| 8.0.0 | 4 / 1 | |
| 7.0.0 | 4 / 1 | |
| 6.0.0 | 4 / 1 | |
| 5.0.0 | 4 / 1 | |
| 4.0.0 | 4 / 1 | |
| 3.0.0 | 4 / 1 | |
| 2.0.1 | 4 / 0 | |
| 2.0.0 | 4 / 0 | |
| 1.47.0 | 4 / 1 | |
| 1.45.6 | 4 / 0 | |
| 1.45.5 | 4 / 0 | |
| 1.45.4 | 4 / 0 | |
| 1.45.3 | 4 / 0 | |
| 1.45.2 | 4 / 0 | |
| 1.45.1 | 4 / 0 | |
| 1.45.0 | 4 / 0 | |
| 1.44.1 | 4 / 0 |
v40.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v40.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v40.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v36.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v35.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v35.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v34.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v34.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v33.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v31.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.