← Home

@liner-fe/icon

npm
51
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

eliot-linerzeze-liner

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal org package (@liner-fe); sparse metadata is consistent across 145 versions, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Internal org package; missing description is a stable pattern, not a malice signal. ai
provenance no-provenance AI (provenance): No provenance is common for internal org packages; stable pattern across versions. ai

Versions (showing 51 of 57)

View all versions
Version Deps Published
2.2.3 2 / 4
2.2.2 2 / 4
2.2.1 2 / 4
2.2.0 2 / 4
2.1.0 2 / 4
2.0.30 2 / 4
2.0.29 2 / 4
2.0.28 2 / 4
2.0.27 2 / 4
2.0.26 2 / 4
2.0.25 2 / 4
2.0.24 2 / 4
2.0.23 2 / 4
2.0.22 2 / 4
2.0.21 2 / 4
2.0.20 2 / 4
2.0.16 2 / 4
2.0.15 2 / 4
2.0.14 2 / 4
2.0.13 2 / 4
2.0.12 2 / 4
2.0.11 2 / 4
1.0.0 2 / 4
0.2.77 2 / 4
0.2.76 2 / 4
0.2.75 2 / 4
0.2.74 2 / 4
0.2.73 2 / 4
0.2.72 2 / 4
0.2.71 2 / 4
0.2.70 2 / 4
0.2.69 2 / 4
0.2.68 2 / 4
0.2.67 2 / 4
0.2.66 2 / 4
0.2.65 2 / 4
0.2.64 2 / 4
0.2.63 2 / 4
0.2.62 2 / 4
0.2.61 2 / 4
0.2.60 2 / 4
0.2.59 2 / 4
0.2.58 2 / 4
0.2.57 2 / 4
0.2.56 2 / 4
0.2.54 2 / 4
0.2.52 2 / 4
0.2.49 2 / 4
0.2.48 2 / 4
0.2.46 2 / 4
0.2.44 2 / 4

v2.2.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.

v2.2.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.

v2.2.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.

v2.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.

v2.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.

v2.0.30

1 finding
INFO No provenance attestation provenance

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

v2.0.29

1 finding
INFO No provenance attestation provenance

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

v2.0.28

1 finding
INFO No provenance attestation provenance

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

v2.0.27

1 finding
INFO No provenance attestation provenance

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

v2.0.26

1 finding
INFO No provenance attestation provenance

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

v2.0.25

1 finding
INFO No provenance attestation provenance

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

v2.0.24

1 finding
INFO No provenance attestation provenance

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