@asphalt-react/layout
Layout
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): Stale publisher change (232d live) consistent with legitimate handoff, not takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change with no takeover pattern; diff shows no material changes. | ai | |
| phantom-deps | phantom-dep:@asphalt-react/helper | AI (phantom-deps): Same-org sibling runtime dependency; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.15.3 | 2 / 3 | |
| 2.15.1 | 2 / 3 | |
| 2.15.0 | 2 / 3 | |
| 2.14.0 | 2 / 3 | |
| 2.13.0 | 2 / 3 | |
| 2.12.2 | 3 / 3 | |
| 2.12.1 | 3 / 3 | |
| 2.12.0 | 3 / 3 | |
| 2.11.0 | 3 / 3 | |
| 2.10.0 | 3 / 3 |
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.12.1
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-12-19, 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.12.0
2 findingsThis version was published by a different npm account (antoniomontana) than the most recent previously approved version (yessyprmtsr) on 2025-11-28. It has since remained available on npm for 232 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.