@asphalt-react/textfield
Textfield
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher already listed as known maintainer; internal team rotation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): inputmask is a well-known masking lib, fits textfield's function. | ai | |
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Same-org monorepo sibling; stable pattern across all @asphalt-react packages. | ai | |
| dependencies | unvetted-dep:@asphalt-react/iconpack | AI (dependencies): Same-org monorepo sibling; stable pattern across all @asphalt-react packages. | ai | |
| dependencies | unvetted-dep:@asphalt-react/qualifier | AI (dependencies): Same-org monorepo sibling; stable pattern across all @asphalt-react packages. | ai | |
| dependencies | unvetted-dep:@asphalt-react/selection | AI (dependencies): Same-org monorepo sibling; stable pattern across all @asphalt-react packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.15.3 | 11 / 4 | |
| 2.15.1 | 11 / 4 | |
| 2.15.0 | 11 / 4 | |
| 2.14.0 | 11 / 4 | |
| 2.13.0 | 11 / 4 | |
| 2.12.2 | 12 / 4 | |
| 2.12.1 | 12 / 4 | |
| 2.12.0 | 12 / 4 | |
| 2.11.0 | 12 / 4 | |
| 2.10.0 | 12 / 4 | |
| 2.9.0 | 11 / 4 | |
| 2.8.1 | 11 / 4 | |
| 2.8.0 | 11 / 4 | |
| 2.6.0 | 11 / 4 | |
| 2.5.1 | 11 / 4 | |
| 2.5.0 | 11 / 4 | |
| 2.4.0 | 11 / 4 | |
| 2.3.0 | 8 / 4 | |
| 2.1.0 | 7 / 4 | |
| 2.0.2 | 7 / 4 | |
| 2.0.1 | 7 / 4 | |
| 2.0.0 | 7 / 4 |
v2.15.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (elayudhanira-gojek) than the most recent previously approved version (yessyprmtsr) on 2026-07-07, but elayudhanira-gojek is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (elayudhanira-gojek) than the most recent previously approved version (yessyprmtsr) on 2025-04-11, but elayudhanira-gojek is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.