@instructure/ui-number-input
A UI component library made by Instructure Inc.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this monorepo package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org same-version sibling @instructure/ui-themes; consistent with monorepo internal refactoring pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all Instructure org members; consistent with team expansion, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-wide CI/CD migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainer alongside org-wide team changes; no malicious signal. | ai | |
| dependencies | unvetted-dep:@instructure/ui-testable | AI (dependencies): Same Instructure org scope; standard internal dependency for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all @instructure/* packages. | ai | |
| phantom-deps | phantom-dep:@instructure/ui-utils | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@instructure/uid | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.7.3 | 11 / 6 | |
| 11.7.2 | 10 / 7 | |
| 11.7.1 | 10 / 7 | |
| 11.7.0 | 10 / 7 | |
| 11.6.0 | 10 / 7 | |
| 11.5.0 | 10 / 7 | |
| 11.4.0 | 10 / 7 | |
| 11.3.0 | 10 / 7 | |
| 11.2.0 | 10 / 7 | |
| 11.0.1 | 9 / 7 | |
| 11.0.0 | 9 / 7 | |
| 10.30.0 | 11 / 7 | |
| 10.29.0 | 11 / 7 | |
| 10.26.4 | 11 / 7 | |
| 10.26.3 | 11 / 7 |
v11.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.26.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.