@instructure/platform-widget-dashboard
A flexible, extensible dashboard system for Canvas LMS that allows students to customize their learning experience with various widgets.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@instructure/platform-canvas-fetch | AI (dependencies): Same @instructure org scope; consistent with this package's monorepo pattern. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Same pattern — declared dep used indirectly or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:sanitize-html | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@instructure/platform-alerts | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared runtime dep in a component library; phantom-dep heuristic fires on re-exported or config-only usage. | ai | |
| phantom-deps | phantom-dep:@instructure/platform-canvas-fetch | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@instructure/platform-graphql-types | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@tanstack/query-persist-client-core | AI (phantom-deps): Declared runtime dep used in config/setup; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@instructure/platform-datetime | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 8 / 49 | |
| 5.2.0 | 8 / 49 | |
| 5.1.0 | 7 / 49 | |
| 4.2.0 | 7 / 15 | |
| 4.1.0 | 7 / 15 | |
| 4.0.3 | 4 / 15 | |
| 4.0.2 | 4 / 15 | |
| 4.0.1 | 4 / 15 | |
| 4.0.0 | 4 / 15 | |
| 3.3.0 | 4 / 15 | |
| 3.2.1 | 4 / 15 | |
| 3.2.0 | 4 / 15 | |
| 3.1.2 | 4 / 15 | |
| 3.1.1 | 4 / 15 | |
| 3.1.0 | 4 / 15 | |
| 3.0.0 | 4 / 14 | |
| 2.0.0 | 4 / 14 | |
| 1.1.0 | 4 / 14 | |
| 1.0.0 | 4 / 14 | |
| 0.5.0 | 4 / 14 | |
| 0.4.0 | 4 / 14 | |
| 0.3.0 | 4 / 14 | |
| 0.2.1 | 4 / 14 | |
| 0.2.0 | 4 / 14 | |
| 0.1.0 | 4 / 14 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.