@instructure/platform-study-assist
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for non-public libraries. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 1 / 26 | |
| 1.1.0 | 1 / 26 | |
| 1.0.0 | 1 / 15 | |
| 0.12.1 | 1 / 15 | |
| 0.12.0 | 1 / 15 | |
| 0.11.1 | 1 / 15 | |
| 0.11.0 | 1 / 15 | |
| 0.10.0 | 1 / 14 | |
| 0.9.0 | 1 / 13 | |
| 0.8.0 | 1 / 13 | |
| 0.7.0 | 1 / 13 | |
| 0.6.0 | 1 / 13 | |
| 0.5.0 | 1 / 13 | |
| 0.4.0 | 1 / 13 | |
| 0.3.0 | 1 / 13 | |
| 0.2.0 | 1 / 13 | |
| 0.1.1 | 1 / 13 | |
| 0.1.0 | 1 / 13 |
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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.