@instructure/platform-institutional-tagging
Institutions need a flexible system for categorizing and tracking users, courses and other resources beyond Canvas’s built-in organizational structures.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Instructure org package published via GitHub Actions CI; no provenance attestation is a process gap, not a security signal here. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): luxon is a declared runtime dep; phantom-dep fires due to indirect/type-only imports in this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dep; phantom-dep fires due to indirect/type-only imports in this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 4 / 44 | |
| 6.6.0 | 4 / 44 | |
| 6.5.1 | 3 / 46 | |
| 6.4.0 | 3 / 26 | |
| 6.3.0 | 3 / 26 | |
| 6.2.0 | 3 / 26 | |
| 6.1.0 | 3 / 26 | |
| 6.0.1 | 3 / 26 | |
| 6.0.0 | 3 / 26 | |
| 5.1.0 | 3 / 26 | |
| 5.0.1 | 3 / 26 | |
| 5.0.0 | 3 / 26 | |
| 4.0.0 | 3 / 26 | |
| 3.0.2 | 5 / 25 | |
| 3.0.1 | 5 / 25 | |
| 3.0.0 | 5 / 25 | |
| 2.0.0 | 4 / 25 |
v7.0.0
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.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.