@stack-spot/portal-layout
Implements the general layout for a Stackspot web application.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publisher within same scope; benign automation transition. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is not yet standard practice; absence is not a security risk for this established package. | ai | |
| dependencies | unvetted-dep:reactour | AI (dependencies): reactour is a well-known React guided-tour library; stable dependency for this UI layout package. | ai |
Versions (showing 51 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.43.3 | 3 / 23 | |
| 2.43.2 | 3 / 23 | |
| 2.43.1 | 3 / 23 | |
| 2.43.0 | 3 / 23 | |
| 2.42.3 | 3 / 23 | |
| 2.42.2 | 3 / 23 | |
| 2.42.1 | 3 / 23 | |
| 2.42.0 | 3 / 22 | |
| 2.41.0 | 3 / 22 | |
| 2.40.0 | 3 / 22 | |
| 2.39.0 | 3 / 22 | |
| 2.38.1 | 2 / 21 | |
| 2.38.0 | 2 / 21 | |
| 2.37.1 | 2 / 21 | |
| 2.37.0 | 2 / 21 | |
| 2.36.3 | 2 / 21 | |
| 2.36.2 | 2 / 21 | |
| 2.36.1 | 2 / 21 | |
| 2.36.0 | 2 / 21 | |
| 2.35.1 | 2 / 21 | |
| 2.35.0 | 2 / 21 | |
| 2.34.2 | 2 / 21 | |
| 2.34.1 | 2 / 21 | |
| 2.34.0 | 2 / 21 | |
| 2.33.1 | 2 / 21 | |
| 2.33.0 | 2 / 21 | |
| 2.32.5 | 2 / 21 | |
| 2.32.4 | 2 / 21 | |
| 2.32.3 | 2 / 21 | |
| 2.32.2 | 2 / 21 | |
| 2.32.1 | 2 / 21 | |
| 2.32.0 | 2 / 21 | |
| 2.31.1 | 2 / 21 | |
| 2.31.0 | 2 / 21 | |
| 2.30.0 | 2 / 21 | |
| 2.29.1 | 2 / 21 | |
| 2.29.0 | 2 / 21 | |
| 2.28.1 | 2 / 21 | |
| 2.28.0 | 2 / 21 | |
| 2.27.0 | 2 / 21 | |
| 2.26.1 | 2 / 21 | |
| 2.26.0 | 2 / 21 | |
| 2.25.3 | 2 / 21 | |
| 2.25.2 | 2 / 21 | |
| 2.25.1 | 2 / 21 | |
| 2.25.0 | 2 / 21 | |
| 2.24.1 | 2 / 21 | |
| 2.24.0 | 2 / 21 | |
| 2.23.3 | 2 / 21 | |
| 2.23.2 | 2 / 21 | |
| 2.23.1 | 2 / 21 |
v2.43.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.42.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.40.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.