@midscene/playground-app
Reusable React shell for Midscene playground applications
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA Sigstore attestation; stable pattern for this package going forward. | ai | |
| source-diff | obfuscated-file:dist/lib/icons/midscene-logo.js | AI (source-diff): File is standard rslib/webpack-bundled React icon component output, not obfuscation. Long lines are SVG path data or minified JSX — consistent with this package's build tooling. | ai | |
| source-diff | obfuscated-file:dist/es/icons/midscene-logo.mjs | AI (source-diff): ESM counterpart of the same logo component bundle. Same rationale: minified build output, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the active midscene monorepo with 115 versions; short README and no keywords are quality issues, not security signals. | ai | |
| provenance | no-provenance | AI (provenance): Legitimate open-source project from web-infra-dev org; lack of provenance is common and not a security concern here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 8 / 13 | |
| 1.9.0 | 8 / 13 | |
| 1.8.11 | 8 / 13 | |
| 1.8.9 | 8 / 13 | |
| 1.8.8 | 8 / 13 | |
| 1.8.7 | 8 / 13 | |
| 1.8.6 | 8 / 13 | |
| 1.8.5 | 8 / 13 | |
| 1.8.4 | 8 / 13 | |
| 1.8.2 | 8 / 13 | |
| 1.8.1 | 8 / 13 | |
| 1.8.0 | 8 / 13 | |
| 1.7.10 | 8 / 13 | |
| 1.7.9 | 8 / 13 | |
| 1.7.7 | 8 / 13 | |
| 1.7.6 | 8 / 13 | |
| 1.7.5 | 8 / 13 | |
| 1.7.4 | 8 / 13 | |
| 1.7.3 | 7 / 13 | |
| 1.7.2 | 7 / 13 | |
| 1.7.1 | 7 / 13 | |
| 1.7.0 | 7 / 13 | |
| 1.6.4 | 7 / 13 | |
| 1.6.3 | 7 / 12 | |
| 1.6.2 | 7 / 12 | |
| 1.6.1 | 7 / 12 | |
| 1.6.0 | 7 / 12 | |
| 1.5.8 | 7 / 12 | |
| 1.5.7 | 4 / 12 | |
| 1.5.6 | 4 / 12 | |
| 1.5.5 | 4 / 12 |
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.