@brightspace-ui/core
A collection of accessible, free, open-source web components for building Brightspace applications
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): d2l-travis-deploy CI automation routinely publishes rapidly; consistent with this package's history. | ai | |
| dependencies | unvetted-dep:ifrau | AI (dependencies): Long-standing dependency of this package; not a new addition. | ai | |
| dependencies | unvetted-dep:@brightspace-ui/intl | AI (dependencies): First-party D2L scoped package; stable long-term dependency. | ai | |
| dependencies | unvetted-dep:@brightspace-ui/lms-context-provider | AI (dependencies): First-party D2L scoped package; stable long-term dependency. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @brightspace-ui/core is a legitimate D2L component library; Levenshtein match to 'cors' is a false positive. | ai |
Versions (showing 100 of 260)
| Version | Deps | Published |
|---|---|---|
| 3.239.1 | 6 / 20 | |
| 3.239.0 | 6 / 20 | |
| 3.238.0 | 6 / 20 | |
| 3.237.6 | 6 / 20 | |
| 3.237.5 | 6 / 20 | |
| 3.237.4 | 6 / 20 | |
| 3.237.3 | 6 / 20 | |
| 3.237.2 | 6 / 20 | |
| 3.237.1 | 6 / 20 | |
| 3.237.0 | 6 / 20 | |
| 3.236.0 | 6 / 20 | |
| 3.235.2 | 6 / 20 | |
| 3.235.1 | 6 / 20 | |
| 3.235.0 | 6 / 20 | |
| 3.234.2 | 6 / 19 | |
| 3.234.1 | 6 / 19 | |
| 3.234.0 | 6 / 19 | |
| 3.233.0 | 6 / 19 | |
| 3.232.1 | 6 / 19 | |
| 3.232.0 | 6 / 19 | |
| 3.231.0 | 6 / 19 | |
| 3.230.0 | 6 / 19 | |
| 3.229.0 | 6 / 19 | |
| 3.228.3 | 6 / 19 | |
| 3.228.2 | 6 / 19 | |
| 3.228.1 | 6 / 19 | |
| 3.228.0 | 6 / 19 | |
| 3.227.16 | 6 / 19 | |
| 3.227.15 | 6 / 19 | |
| 3.227.14 | 6 / 19 | |
| 3.227.13 | 6 / 19 | |
| 3.227.12 | 6 / 19 | |
| 3.227.11 | 6 / 19 | |
| 3.227.10 | 6 / 19 | |
| 3.227.9 | 6 / 19 | |
| 3.227.8 | 6 / 19 | |
| 3.227.7 | 6 / 19 | |
| 3.227.6 | 6 / 19 | |
| 3.227.5 | 6 / 19 | |
| 3.227.4 | 6 / 19 | |
| 3.227.3 | 6 / 19 | |
| 3.227.2 | 6 / 19 | |
| 3.227.1 | 6 / 19 | |
| 3.227.0 | 6 / 19 | |
| 3.226.0 | 6 / 19 | |
| 3.225.1 | 6 / 19 | |
| 3.225.0 | 6 / 19 | |
| 3.224.0 | 6 / 19 | |
| 3.223.0 | 6 / 19 | |
| 3.222.1 | 6 / 19 | |
| 3.222.0 | 6 / 19 | |
| 3.221.2 | 6 / 19 | |
| 3.221.1 | 6 / 19 | |
| 3.221.0 | 7 / 19 | |
| 3.220.3 | 7 / 19 | |
| 3.220.2 | 7 / 19 | |
| 3.220.1 | 7 / 19 | |
| 3.220.0 | 7 / 19 | |
| 3.219.10 | 7 / 19 | |
| 3.219.9 | 7 / 19 | |
| 3.219.8 | 7 / 19 | |
| 3.219.7 | 7 / 19 | |
| 3.219.6 | 7 / 19 | |
| 3.219.5 | 7 / 19 | |
| 3.219.4 | 7 / 19 | |
| 3.219.3 | 7 / 19 | |
| 3.219.2 | 7 / 19 | |
| 3.219.1 | 7 / 19 | |
| 3.219.0 | 7 / 19 | |
| 3.218.2 | 7 / 19 | |
| 3.218.1 | 7 / 19 | |
| 3.218.0 | 7 / 19 | |
| 3.217.0 | 7 / 19 | |
| 3.216.1 | 7 / 19 | |
| 3.216.0 | 7 / 19 | |
| 3.215.0 | 7 / 19 | |
| 3.214.0 | 7 / 19 | |
| 3.213.1 | 7 / 19 | |
| 3.213.0 | 7 / 19 | |
| 3.212.0 | 7 / 19 | |
| 3.211.0 | 7 / 19 | |
| 3.210.0 | 7 / 19 | |
| 3.209.1 | 7 / 19 | |
| 3.209.0 | 7 / 19 | |
| 3.208.6 | 7 / 19 | |
| 3.208.5 | 7 / 19 | |
| 3.208.4 | 7 / 19 | |
| 3.208.3 | 7 / 19 | |
| 3.208.2 | 7 / 19 | |
| 3.208.1 | 7 / 19 | |
| 3.208.0 | 7 / 19 | |
| 3.207.1 | 7 / 19 | |
| 3.207.0 | 7 / 19 | |
| 3.206.3 | 7 / 19 | |
| 3.206.2 | 7 / 19 | |
| 3.206.1 | 7 / 19 | |
| 3.206.0 | 7 / 19 | |
| 3.205.2 | 7 / 19 | |
| 3.205.1 | 7 / 19 | |
| 3.205.0 | 7 / 19 |
v3.227.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.227.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.226.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.225.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.225.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.224.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.223.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.222.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.222.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.221.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.221.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.221.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.220.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.220.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.220.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.220.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.219.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.218.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.218.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.217.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.216.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.214.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.213.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.209.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.207.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.207.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.206.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.206.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.206.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.206.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.205.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.205.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.205.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.