@projectstorm/react-workspaces-core
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): CI/CD provenance-attested transition, flagged as improvement not compromise | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-download niche library with sparse but legitimate release cadence | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Direct runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Direct runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:color | AI (phantom-deps): Direct runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo workspace package; missing metadata is typical and not indicative of spam. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 7 / 4 | |
| 4.3.1 | 7 / 4 | |
| 4.3.0 | 7 / 4 | |
| 4.2.3 | 7 / 4 | |
| 4.2.2 | 7 / 4 | |
| 4.2.1 | 7 / 4 | |
| 4.2.0 | 7 / 4 | |
| 4.1.1 | 7 / 4 | |
| 4.1.0 | 7 / 4 | |
| 4.0.0 | 7 / 4 |
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-10. 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.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.