← Home

@syncfusion/ej2-angular-splitbuttons

npm Repository Homepage
8
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

syncfusionorgessentialjs2syncfusion-javascript

Keywords

angularngej2-ng-splitbuttonsng-splitbuttonng-dropdownbuttonng progress buttonangular progress buttonng spin buttonangular spin buttonng progressangular progressng progress indicatorangular progress indicatorng spinnerangular spinner

Versions (showing 8 of 8)

Version Deps Published
34.1.29 3 / 0
33.2.6 3 / 0
33.2.3 3 / 0
33.1.49 3 / 0
33.1.44 3 / 0
32.2.7 3 / 0
32.2.3 3 / 0
32.1.24 3 / 0

v34.1.29

1 finding
LOW No provenance attestation provenance

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

v33.2.6

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.

v33.2.3

1 finding
LOW No provenance attestation provenance

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

v33.1.49

1 finding
LOW No provenance attestation provenance

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

v33.1.44

1 finding
LOW No provenance attestation provenance

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

v32.2.7

1 finding
LOW No provenance attestation provenance

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

v32.2.3

1 finding
LOW No provenance attestation provenance

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

v32.1.24

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.