← Home

@primeuix/styled

npm
29
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mert.sincancagatay.civici

Keywords

styledcssstyle utilitiesprimengprimereactprimevueprimeuix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Sparse metadata typical of early monorepo package versions; publisher and downloads confirm legitimacy. ai
npm-metadata no-description AI (npm-metadata): Minor metadata gap, not a malware indicator for this trusted package. ai
source-diff obfuscated-file:dist/index.mjs AI (source-diff): Standard tsup-minified ESM bundle; sample shows legitimate CSS utility code, not obfuscation. ai
semgrep semgrep:new-function-constructor AI (semgrep): Used as a design-token template compiler with controlled interpolated input; stable pattern for this package. ai
provenance no-provenance AI (provenance): PrimeTek/primefaces org packages consistently lack Sigstore provenance; stable false positive for this package family. ai

Versions (showing 29 of 29)

Version Deps Published
1.0.0 2 / 0
0.7.4 1 / 0
0.7.3 1 / 0
0.7.2 1 / 0
0.7.1 1 / 0
0.7.0 1 / 0
0.6.4 1 / 0
0.6.3 1 / 0
0.6.2 1 / 0
0.6.1 1 / 0
0.6.0 1 / 0
0.5.1 1 / 0
0.5.0 1 / 0
0.4.1 1 / 0
0.4.0 1 / 0
0.3.2 1 / 0
0.3.1 1 / 0
0.3.0 1 / 0
0.2.0 1 / 0
0.1.3 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0
0.1.0 1 / 0
0.0.6 1 / 0
0.0.5 1 / 0
0.0.4 1 / 0
0.0.3 1 / 0
0.0.2 1 / 0
0.0.1 0 / 0

v1.0.0

1 finding
INFO No provenance attestation provenance

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

v0.5.1

1 finding
INFO No provenance attestation provenance

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

v0.5.0

1 finding
INFO No provenance attestation provenance

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

v0.4.1

1 finding
INFO No provenance attestation provenance

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

v0.4.0

1 finding
INFO No provenance attestation provenance

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

v0.3.2

1 finding
INFO No provenance attestation provenance

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

v0.3.1

1 finding
INFO No provenance attestation provenance

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

v0.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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

v0.0.6

1 finding
INFO No provenance attestation provenance

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

v0.0.5

1 finding
INFO No provenance attestation provenance

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

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.