@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 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 2 / 21 | |
| 2.3.0 | 2 / 21 | |
| 2.2.0 | 2 / 21 | |
| 2.1.1 | 2 / 21 | |
| 2.1.0 | 2 / 21 | |
| 2.0.1 | 2 / 21 | |
| 2.0.0 | 2 / 21 |
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.