← Home

@igniteui/angular-templates

Templates for Ignite UI for Angular projects and components

6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

igniteui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Large vendor (Infragistics) with 400+ versions; templated naming and sparse README are normal for this package family. ai
dependencies unvetted-dep:@igniteui/cli-core AI (dependencies): Sibling package from the same Infragistics/IgniteUI org; not a third-party risk. ai

Versions (showing 6 of 6)

Version Deps Published
21.2.1522 2 / 0
21.2.1521 2 / 0
21.2.1520 2 / 0
21.2.1510 2 / 0
21.2.1501 2 / 0
21.2.1500 2 / 0

v21.2.1522

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v21.2.1521

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v21.2.1520

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v21.2.1510

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v21.2.1501

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v21.2.1500

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.