@salutejs/plasma-hope
Salute Design System / Internal React UI kit for web applications
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:storeon | AI (phantom-deps): storeon is a declared runtime dep used indirectly; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Peer dep of react-popper; declared for version pinning, not directly imported by package code. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 1.380.0 | 6 / 30 | |
| 1.378.0 | 6 / 30 | |
| 1.377.0 | 6 / 30 | |
| 1.375.0 | 7 / 30 | |
| 1.373.0 | 7 / 30 | |
| 1.371.0 | 7 / 31 | |
| 1.370.0 | 7 / 31 | |
| 1.369.0 | 7 / 31 | |
| 1.368.0 | 7 / 31 | |
| 1.367.0 | 7 / 31 | |
| 1.366.0 | 7 / 31 | |
| 1.365.0 | 7 / 31 | |
| 1.364.0 | 7 / 31 | |
| 1.363.0 | 7 / 31 | |
| 1.360.0 | 7 / 31 | |
| 1.359.0 | 7 / 31 | |
| 1.358.0 | 7 / 31 | |
| 1.357.0 | 7 / 31 | |
| 1.356.0 | 7 / 31 | |
| 1.355.0 | 7 / 31 | |
| 1.354.0 | 7 / 31 | |
| 1.353.0 | 7 / 31 | |
| 1.352.0 | 7 / 31 | |
| 1.351.0 | 7 / 31 | |
| 1.349.0 | 7 / 31 | |
| 1.348.0 | 7 / 31 | |
| 1.346.0 | 7 / 31 | |
| 1.344.0 | 7 / 31 | |
| 1.343.0 | 7 / 31 | |
| 1.342.0 | 7 / 31 | |
| 1.340.0 | 7 / 31 | |
| 1.339.0 | 7 / 31 | |
| 1.338.0 | 7 / 31 | |
| 1.336.0 | 7 / 31 | |
| 1.335.0 | 7 / 31 | |
| 1.331.0 | 7 / 31 | |
| 1.330.0 | 7 / 31 | |
| 1.329.0 | 7 / 31 | |
| 1.327.0 | 7 / 31 | |
| 1.324.0 | 7 / 32 | |
| 1.322.0 | 7 / 32 | |
| 1.320.0 | 7 / 32 | |
| 1.317.0 | 7 / 32 | |
| 1.315.0 | 7 / 32 | |
| 1.313.0 | 7 / 32 | |
| 1.312.0 | 7 / 32 | |
| 1.310.0 | 7 / 32 | |
| 1.306.0 | 7 / 32 | |
| 1.302.0 | 7 / 32 | |
| 1.292.0 | 7 / 32 | |
| 1.290.0 | 7 / 32 | |
| 1.288.0 | 7 / 32 | |
| 1.285.0 | 7 / 32 | |
| 1.281.0 | 7 / 32 | |
| 1.280.0 | 7 / 32 | |
| 1.279.0 | 7 / 32 | |
| 1.278.0 | 7 / 32 | |
| 1.276.0 | 7 / 32 | |
| 1.273.0 | 7 / 32 | |
| 1.270.0 | 7 / 32 | |
| 1.267.1 | 7 / 32 | |
| 1.267.0 | 7 / 32 | |
| 1.263.0 | 7 / 32 | |
| 1.258.0 | 7 / 32 | |
| 1.255.1 | 7 / 32 | |
| 1.255.0 | 7 / 32 | |
| 1.250.0 | 7 / 32 | |
| 1.248.0 | 7 / 32 | |
| 1.247.0 | 7 / 32 | |
| 1.244.0 | 7 / 32 | |
| 1.238.0 | 7 / 39 | |
| 1.236.0 | 7 / 39 | |
| 1.235.0 | 7 / 39 | |
| 1.227.0 | 7 / 39 | |
| 1.225.0 | 7 / 39 | |
| 1.221.0 | 7 / 39 | |
| 1.220.0 | 7 / 39 | |
| 1.219.0 | 7 / 39 | |
| 1.218.0 | 7 / 39 | |
| 1.217.0 | 8 / 39 | |
| 1.216.0 | 8 / 39 | |
| 1.215.0 | 8 / 39 | |
| 1.214.0 | 8 / 39 | |
| 1.213.0 | 8 / 39 | |
| 1.212.0 | 8 / 39 | |
| 1.211.0 | 8 / 39 | |
| 1.210.0 | 8 / 39 | |
| 1.209.0 | 8 / 39 | |
| 1.208.2 | 8 / 39 | |
| 1.208.1 | 8 / 39 | |
| 1.208.0 | 8 / 39 | |
| 1.207.0 | 8 / 39 | |
| 1.206.0 | 8 / 39 | |
| 1.205.0 | 8 / 39 | |
| 1.204.1 | 8 / 39 | |
| 1.204.0 | 8 / 39 | |
| 1.203.0 | 8 / 39 | |
| 1.202.0 | 8 / 39 | |
| 1.201.0 | 8 / 39 |
v1.380.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.378.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.339.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.338.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.336.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.335.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.331.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.330.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.329.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.327.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.324.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.322.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.320.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.317.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.313.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.310.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.302.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.292.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.285.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.281.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.280.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.279.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.278.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.276.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.273.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.270.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.267.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.263.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.258.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.255.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.255.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.250.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.244.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.238.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.236.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.235.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.227.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.225.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.220.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.219.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.217.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.214.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.210.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.208.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.208.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.207.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.205.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.204.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.204.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.203.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.