@nolebase/ui
A collection of Vue components Nolebase uses.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @nolebase/ui; not a typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @nolebase/ui; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @nolebase/ui; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @nolebase/ui; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @nolebase/ui; not a typosquat of yup. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): less is a declared runtime dep used in build/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@iconify-json/octicon | AI (phantom-deps): Icon data dep referenced in config; stable false positive for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.18.2 | 2 / 0 | |
| 2.18.1 | 2 / 0 | |
| 2.18.0 | 3 / 0 | |
| 2.17.2 | 3 / 0 | |
| 2.17.1 | 3 / 0 | |
| 2.17.0 | 3 / 0 | |
| 2.16.0 | 3 / 0 | |
| 2.15.1 | 3 / 0 | |
| 2.15.0 | 3 / 0 | |
| 2.14.0 | 3 / 0 | |
| 2.13.7 | 3 / 0 | |
| 2.13.6 | 3 / 0 | |
| 2.13.5 | 3 / 1 | |
| 2.13.2 | 3 / 1 | |
| 2.13.1 | 3 / 1 | |
| 2.13.0 | 3 / 1 | |
| 2.12.1 | 4 / 1 | |
| 2.12.0 | 4 / 1 | |
| 2.11.1 | 4 / 1 | |
| 2.11.0 | 4 / 1 | |
| 2.10.0 | 4 / 1 | |
| 2.9.0 | 4 / 1 | |
| 2.8.1 | 4 / 1 | |
| 2.8.0 | 4 / 1 | |
| 2.7.0 | 4 / 1 | |
| 2.6.1 | 4 / 1 | |
| 2.6.0 | 4 / 1 | |
| 2.5.0 | 4 / 1 | |
| 2.4.0 | 4 / 1 | |
| 2.3.0 | 4 / 1 | |
| 2.2.2 | 4 / 1 | |
| 2.2.1 | 4 / 1 | |
| 2.2.0 | 4 / 1 | |
| 2.1.2 | 2 / 1 | |
| 2.1.1 | 2 / 1 | |
| 2.1.0 | 2 / 1 | |
| 2.0.0 | 2 / 1 |
v2.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.