@instructure/platform-grades
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Declared dep referenced in config; common pattern for build-time or transitive use. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @instructure org CI-published package; sparse metadata is expected for early-stage monorepo packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same rationale — internal tooling package, missing description is cosmetic. | ai | |
| phantom-deps | phantom-dep:@instructure/platform-graphql-types | AI (phantom-deps): Same-org dep; phantom-dep heuristic likely fires due to indirect/type-only import patterns. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 8 / 27 | |
| 0.2.1 | 8 / 27 | |
| 0.1.0 | 8 / 16 | |
| 0.0.4 | 5 / 15 | |
| 0.0.3 | 5 / 15 | |
| 0.0.2 | 5 / 15 |
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Package 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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.