← Home

@limetech/limepkg-cpq-order

npm

Type definitions for limepkg-cpq-order frontend

33
Versions
Apache-2.0
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

flipparecybercapspecularrainanderssonjohanlime-ci

Keywords

limepkgcpq-ordertypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal Lime Technologies component package; sparse metadata is normal, no malicious behavior found. ai
provenance publisher-changed AI (provenance): CI account with 95 approved packages / 0 rejected; consistent org-wide publishing migration. ai
maintainer-change maintainer-added AI (maintainer-change): Corresponds to same trusted lime-ci CI publisher transition. ai

Versions (showing 33 of 33)

Version Deps Published
2.15.0 0 / 1
2.14.8 0 / 1
2.14.7 0 / 1
2.14.6 0 / 1
2.14.5 0 / 1
2.14.4 0 / 1
2.14.3 0 / 1
2.14.2 0 / 1
2.14.1 0 / 1
2.14.0 0 / 1
2.13.0 0 / 1
2.12.5 0 / 1
2.12.4 0 / 1
2.12.3 0 / 1
2.12.2 0 / 1
2.12.1 0 / 1
2.12.0 0 / 1
2.11.3 0 / 1
2.11.2 0 / 1
2.11.1 0 / 1
2.11.0 0 / 1
2.10.9 0 / 1
2.10.8 0 / 1
2.10.7 0 / 1
2.10.6 0 / 1
2.10.5 0 / 1
2.10.4 0 / 0
2.10.3 0 / 17
2.10.2 0 / 17
2.10.0 0 / 17
2.9.1 0 / 17
2.9.0 0 / 17
2.8.0 0 / 17

v2.12.1

2 findings
HIGH Publisher changed: specularrain → lime-ci (on 2025-04-15) provenance

This version was published by a different npm account than previous versions on 2025-04-15. 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.12.0

1 finding
LOW No provenance attestation provenance

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

v2.11.3

1 finding
LOW No provenance attestation provenance

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

v2.11.2

1 finding
LOW No provenance attestation provenance

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

v2.11.1

1 finding
LOW No provenance attestation provenance

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

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.10.9

1 finding
LOW No provenance attestation provenance

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

v2.10.8

1 finding
LOW No provenance attestation provenance

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

v2.10.7

1 finding
LOW No provenance attestation provenance

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

v2.10.6

1 finding
LOW No provenance attestation provenance

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

v2.10.5

1 finding
LOW No provenance attestation provenance

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

v2.10.4

1 finding
LOW No provenance attestation provenance

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

v2.10.3

1 finding
LOW No provenance attestation provenance

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

v2.10.2

1 finding
LOW No provenance attestation provenance

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

v2.10.0

1 finding
LOW No provenance attestation provenance

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

v2.9.1

1 finding
LOW No provenance attestation provenance

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

v2.9.0

1 finding
LOW No provenance attestation provenance

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

v2.8.0

1 finding
LOW No provenance attestation provenance

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