@nysds/nys-fileinput
The Fileinput component from the NYS Design System.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nysds/nys-icon | AI (phantom-deps): Design system component; dependencies are re-exported, not directly imported. | ai | |
| phantom-deps | phantom-dep:@nysds/nys-label | AI (phantom-deps): Design system component; dependencies are re-exported, not directly imported. | ai | |
| phantom-deps | phantom-dep:@nysds/nys-button | AI (phantom-deps): Design system component; dependencies are re-exported, not directly imported. | ai | |
| phantom-deps | phantom-dep:@nysds/nys-errormessage | AI (phantom-deps): Design system component; dependencies are re-exported, not directly imported. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.18.3 | 4 / 3 | |
| 1.18.1 | 4 / 3 | |
| 1.18.0 | 4 / 3 | |
| 1.17.0 | 4 / 3 | |
| 1.16.1 | 4 / 3 | |
| 1.16.0 | 4 / 3 | |
| 1.15.1 | 4 / 3 | |
| 1.15.0 | 4 / 3 | |
| 1.14.0 | 4 / 3 | |
| 1.13.1 | 4 / 3 | |
| 1.13.0 | 4 / 3 | |
| 1.12.0 | 4 / 3 | |
| 1.11.4 | 4 / 3 | |
| 1.11.3 | 4 / 3 | |
| 1.11.2 | 4 / 3 | |
| 1.11.1 | 4 / 3 | |
| 1.11.0 | 4 / 3 | |
| 1.10.1 | 4 / 3 | |
| 1.10.0 | 4 / 3 | |
| 1.9.1 | 4 / 3 | |
| 1.9.0 | 4 / 3 | |
| 1.8.0 | 4 / 3 | |
| 1.7.0 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.3 | 4 / 3 | |
| 1.5.0 | 0 / 7 | |
| 1.4.0 | 0 / 7 |
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.