← Home

@stack-spot/portal-components

npm

A collection of UI components, hooks, SVG images, utilities and variables shared among Stackspot web projects.

51
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

carolinegoncalveszuplarissacostazupmagno.lemoshiltonpaulozuptiagoperesfrarthurbleilzuptarcisiogclucasgarciazuprafamsilva-zupleonardo.paliscaiorezendezupnataliecrissilvastackspotadminwanderzup

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/svg/CS.js AI (source-diff): SVG icon component with long path data, not real obfuscation. ai
source-diff large-new-source-files AI (source-diff): New SVG icon set additions, consistent with component library growth. ai
source-diff obfuscated-file:dist/svg/GenericPlaceholder.js AI (source-diff): SVG icon component with long path data, not real obfuscation. ai
provenance publisher-changed AI (provenance): Org-managed scope transitioning to admin account; publisher has strong track record, no behavior change. ai
maintainer-change maintainer-added AI (maintainer-change): Consistent with same publisher transition; no code changes accompany it. ai
source-diff obfuscated-file:dist/svg/GenericPlaceholderCentered.js AI (source-diff): Long line is SVG path data, not obfuscated code; sample shows plain JSX. ai
publish-pattern new-deps-added AI (publish-pattern): prismjs is a well-known, legitimate syntax-highlighting dependency. ai
provenance missing-githead AI (provenance): Manual publish by known maintainer; gitHead absence is benign env change. ai
maintainer-change maintainer-removed AI (maintainer-change): Publisher is a prior-listed maintainer; no takeover, roster churn within same org. ai
phantom-deps phantom-dep:prismjs AI (phantom-deps): prismjs is a legitimate runtime dep used via react-syntax-highlighter; phantom flag is a stable false positive for this package. ai

Versions (showing 51 of 83)

View all versions
Version Deps Published
2.28.4 11 / 23
2.28.3 11 / 23
2.28.2 11 / 23
2.28.1 10 / 23
2.28.0 10 / 21
2.27.6 10 / 21
2.27.5 10 / 21
2.27.4 10 / 21
2.27.3 10 / 21
2.27.2 10 / 21
2.27.1 10 / 21
2.27.0 10 / 21
2.26.0 10 / 21
2.25.9 10 / 21
2.25.8 10 / 21
2.25.7 10 / 21
2.25.6 10 / 21
2.25.5 10 / 21
2.25.4 10 / 21
2.25.3 10 / 21
2.25.2 10 / 21
2.25.1 10 / 21
2.25.0 10 / 21
2.24.3 10 / 21
2.24.2 10 / 21
2.24.1 10 / 21
2.24.0 10 / 21
2.23.0 10 / 21
2.22.5 10 / 21
2.22.4 10 / 21
2.22.3 10 / 21
2.22.2 10 / 21
2.22.1 10 / 21
2.22.0 10 / 21
2.21.2 9 / 21
2.21.1 9 / 21
2.21.0 9 / 21
2.20.0 9 / 21
2.19.2 9 / 21
2.19.1 9 / 21
2.19.0 9 / 21
2.18.0 9 / 21
2.17.0 9 / 21
2.16.1 9 / 21
2.16.0 9 / 21
2.15.1 8 / 21
2.15.0 8 / 21
2.14.1 8 / 21
2.14.0 8 / 21
2.13.0 8 / 21
2.12.1 8 / 21

v2.28.2

2 findings
HIGH New obfuscated file: dist/svg/GenericPlaceholderCentered.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.28.1

2 findings
HIGH New obfuscated file: dist/svg/GenericPlaceholderCentered.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.28.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.27.2

2 findings
HIGH Publisher changed: rafamsilva-zup → stackspotadmin (on 2025-10-17) provenance

This version was published by a different npm account than previous versions on 2025-10-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.27.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: renanrodrigueszup → rafamsilva-zup (on 2025-10-06, known maintainer) provenance

This version was published by a different npm account (rafamsilva-zup) than the most recent previously approved version (renanrodrigueszup) on 2025-10-06, but rafamsilva-zup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.27.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rafamsilva-zup.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: renanrodrigueszup → rafamsilva-zup (on 2025-10-03, known maintainer) provenance

This version was published by a different npm account (rafamsilva-zup) than the most recent previously approved version (renanrodrigueszup) on 2025-10-03, but rafamsilva-zup is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.22.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.21.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.20.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.