@projectstorm/react-workspaces-behavior-divider-dropzone
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 migration with SLSA attestation, not account compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by monorepo release cadence, no other risk signals. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.4.15 | 3 / 1 | |
| 2.4.14 | 3 / 1 | |
| 2.4.13 | 3 / 1 | |
| 2.4.12 | 3 / 1 | |
| 2.4.11 | 3 / 1 | |
| 2.4.10 | 3 / 1 | |
| 2.4.9 | 3 / 1 | |
| 2.4.8 | 3 / 1 | |
| 2.4.7 | 3 / 1 | |
| 2.4.6 | 3 / 1 | |
| 2.4.5 | 3 / 1 |
v2.4.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.13
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.
v2.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.