@salutejs/plasma-ui
Salute Design System.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-draggable | AI (phantom-deps): react-draggable is a declared runtime dependency in package.json; phantom-dep firing is a false positive for this package. | ai |
Versions (showing 100 of 200)
| Version | Deps | Published |
|---|---|---|
| 1.354.0 | 5 / 35 | |
| 1.353.0 | 5 / 35 | |
| 1.351.0 | 5 / 35 | |
| 1.349.0 | 5 / 35 | |
| 1.347.0 | 5 / 35 | |
| 1.346.0 | 5 / 35 | |
| 1.345.0 | 5 / 35 | |
| 1.344.0 | 5 / 34 | |
| 1.343.0 | 5 / 34 | |
| 1.342.0 | 5 / 34 | |
| 1.341.0 | 5 / 34 | |
| 1.340.0 | 5 / 34 | |
| 1.339.0 | 5 / 34 | |
| 1.336.0 | 5 / 34 | |
| 1.335.0 | 5 / 34 | |
| 1.334.0 | 5 / 34 | |
| 1.333.0 | 5 / 34 | |
| 1.332.0 | 5 / 43 | |
| 1.331.0 | 5 / 43 | |
| 1.330.0 | 5 / 43 | |
| 1.329.0 | 5 / 43 | |
| 1.328.0 | 5 / 43 | |
| 1.327.0 | 5 / 43 | |
| 1.325.0 | 5 / 43 | |
| 1.324.0 | 5 / 43 | |
| 1.322.0 | 5 / 43 | |
| 1.320.0 | 5 / 43 | |
| 1.319.0 | 5 / 43 | |
| 1.318.0 | 5 / 43 | |
| 1.316.0 | 5 / 43 | |
| 1.315.0 | 5 / 43 | |
| 1.314.0 | 5 / 43 | |
| 1.312.0 | 5 / 43 | |
| 1.311.0 | 5 / 43 | |
| 1.306.0 | 5 / 43 | |
| 1.305.0 | 5 / 43 | |
| 1.304.0 | 5 / 43 | |
| 1.302.0 | 5 / 43 | |
| 1.299.0 | 5 / 43 | |
| 1.296.0 | 5 / 43 | |
| 1.293.0 | 5 / 43 | |
| 1.290.0 | 5 / 43 | |
| 1.288.0 | 5 / 43 | |
| 1.286.0 | 5 / 43 | |
| 1.285.0 | 5 / 43 | |
| 1.283.0 | 5 / 43 | |
| 1.279.0 | 5 / 43 | |
| 1.275.0 | 5 / 43 | |
| 1.265.0 | 5 / 43 | |
| 1.261.0 | 5 / 43 | |
| 1.258.0 | 5 / 43 | |
| 1.255.0 | 5 / 43 | |
| 1.250.0 | 5 / 43 | |
| 1.249.0 | 5 / 43 | |
| 1.248.0 | 5 / 43 | |
| 1.247.0 | 5 / 43 | |
| 1.245.0 | 5 / 43 | |
| 1.242.0 | 5 / 43 | |
| 1.239.0 | 5 / 43 | |
| 1.237.1 | 5 / 43 | |
| 1.237.0 | 5 / 43 | |
| 1.233.0 | 5 / 43 | |
| 1.230.0 | 5 / 43 | |
| 1.228.1 | 5 / 43 | |
| 1.228.0 | 5 / 43 | |
| 1.224.0 | 5 / 43 | |
| 1.223.0 | 5 / 43 | |
| 1.221.0 | 5 / 46 | |
| 1.218.0 | 5 / 45 | |
| 1.216.0 | 5 / 45 | |
| 1.215.0 | 5 / 45 | |
| 1.209.0 | 5 / 45 | |
| 1.206.0 | 5 / 45 | |
| 1.202.0 | 5 / 45 | |
| 1.201.0 | 5 / 45 | |
| 1.200.0 | 5 / 45 | |
| 1.199.0 | 5 / 45 | |
| 1.198.0 | 5 / 45 | |
| 1.197.0 | 5 / 45 | |
| 1.196.0 | 5 / 44 | |
| 1.195.0 | 5 / 44 | |
| 1.194.0 | 5 / 44 | |
| 1.193.0 | 5 / 44 | |
| 1.192.0 | 5 / 44 | |
| 1.191.1 | 5 / 44 | |
| 1.191.0 | 5 / 44 | |
| 1.190.0 | 5 / 44 | |
| 1.189.0 | 5 / 44 | |
| 1.188.0 | 5 / 44 | |
| 1.187.0 | 5 / 44 | |
| 1.186.1 | 5 / 44 | |
| 1.186.0 | 5 / 44 | |
| 1.185.0 | 5 / 44 | |
| 1.184.0 | 5 / 44 | |
| 1.183.0 | 5 / 44 | |
| 1.182.0 | 5 / 44 | |
| 1.181.1 | 5 / 45 | |
| 1.181.0 | 5 / 45 | |
| 1.180.1 | 5 / 45 | |
| 1.180.0 | 5 / 45 |
v1.354.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.315.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.314.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.312.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.311.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.306.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.305.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.304.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.302.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.299.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.296.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.293.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.290.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.288.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.286.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.285.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.283.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.279.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.275.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.265.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.261.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.258.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.255.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.250.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.249.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.248.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.247.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.245.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.242.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.239.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.237.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.237.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.233.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.230.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.228.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.228.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.224.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.223.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.221.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.206.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.202.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.199.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.198.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.197.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.196.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.195.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.194.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.193.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.192.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.191.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.191.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.190.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.189.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.188.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.187.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.186.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.186.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.185.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.184.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.183.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.182.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.181.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.181.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.180.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.180.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.