@asphalt-react/card
Card
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Gojek design system package; Levenshtein match to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 3 / 2 | |
| 2.15.0 | 3 / 2 | |
| 2.14.0 | 3 / 2 | |
| 2.13.0 | 3 / 2 | |
| 2.12.2 | 4 / 2 | |
| 2.12.1 | 4 / 2 | |
| 2.11.0 | 4 / 2 | |
| 2.10.0 | 4 / 2 | |
| 2.9.0 | 4 / 2 | |
| 2.8.1 | 4 / 2 | |
| 2.8.0 | 4 / 2 | |
| 2.6.0 | 4 / 2 | |
| 2.1.0 | 4 / 2 | |
| 2.0.2 | 4 / 2 | |
| 2.0.1 | 4 / 2 | |
| 2.0.0 | 4 / 2 |
v2.14.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 (antoniomontana) than the most recent previously approved version (yessyprmtsr) on 2026-03-11, but antoniomontana 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.13.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 (antoniomontana) than the most recent previously approved version (yessyprmtsr) on 2026-02-19, but antoniomontana 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.12.2
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 (yessyprmtsr) than the most recent previously approved version (elayudhanira-gojek) on 2026-01-28, but yessyprmtsr 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.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.