@theme-ui/prism
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): Legitimate long-standing maintainer transfer, stable for years. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change from 2020, long-persisted, not a takeover pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by stable, low-churn utility package. | ai | |
| typosquat | typosquat.levenshtein:prisma | AI (typosquat): Legitimate Theme UI monorepo package; 'prism' refers to syntax highlighting, not the Prisma ORM. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in build-presets.js loads from a hardcoded list of theme names; no user-controlled input. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.17.4 | 2 / 7 | |
| 0.17.2 | 2 / 7 | |
| 0.17.1 | 2 / 7 | |
| 0.17.0 | 2 / 7 | |
| 0.16.2 | 2 / 7 | |
| 0.16.1 | 2 / 7 | |
| 0.16.0 | 2 / 7 | |
| 0.15.7 | 1 / 7 | |
| 0.15.5 | 1 / 7 | |
| 0.15.4 | 1 / 7 | |
| 0.15.3 | 1 / 7 | |
| 0.15.1 | 1 / 6 | |
| 0.15.0 | 1 / 6 | |
| 0.14.7 | 1 / 4 | |
| 0.14.6 | 1 / 4 | |
| 0.14.5 | 1 / 4 | |
| 0.14.4 | 1 / 4 | |
| 0.14.3 | 1 / 4 | |
| 0.14.2 | 1 / 4 | |
| 0.14.1 | 1 / 4 | |
| 0.14.0 | 1 / 4 | |
| 0.13.1 | 1 / 4 | |
| 0.13.0 | 1 / 4 | |
| 0.12.1 | 1 / 4 | |
| 0.12.0 | 1 / 4 | |
| 0.11.3 | 1 / 4 | |
| 0.11.2 | 1 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.0 | 1 / 4 | |
| 0.9.1 | 1 / 4 | |
| 0.9.0 | 1 / 4 | |
| 0.8.4 | 1 / 4 | |
| 0.8.3 | 1 / 4 | |
| 0.8.2 | 1 / 4 | |
| 0.8.1 | 1 / 4 | |
| 0.8.0 | 1 / 4 | |
| 0.7.5 | 1 / 4 | |
| 0.7.4 | 1 / 4 | |
| 0.7.3 | 1 / 4 | |
| 0.7.2 | 1 / 4 | |
| 0.7.1 | 1 / 4 | |
| 0.7.0 | 1 / 4 | |
| 0.6.2 | 1 / 4 | |
| 0.6.1 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.3.5 | 1 / 3 | |
| 0.3.4 | 1 / 3 | |
| 0.3.0 | 1 / 3 | |
| 0.2.50 | 1 / 3 | |
| 0.2.46 | 1 / 3 |
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2024-02-19. It has since remained available on npm for 885 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.
v0.16.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2023-08-14. It has since remained available on npm for 1074 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.
v0.16.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2023-06-15. It has since remained available on npm for 1134 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.
v0.15.7
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2023-03-30. It has since remained available on npm for 1211 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.
v0.15.5
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2023-02-07. It has since remained available on npm for 1262 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.
v0.15.4
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-11-10. It has since remained available on npm for 1351 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.
v0.15.3
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-10-17. It has since remained available on npm for 1375 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.
v0.15.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-09-26. It has since remained available on npm for 1396 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.
v0.15.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-09-26. It has since remained available on npm for 1396 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.
v0.14.7
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-07-28. It has since remained available on npm for 1456 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.
v0.14.6
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-06-15. It has since remained available on npm for 1499 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.
v0.14.5
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-04-30. It has since remained available on npm for 1545 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.
v0.14.4
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-04-23. It has since remained available on npm for 1552 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.
v0.14.3
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-04-21. It has since remained available on npm for 1554 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.
v0.14.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-03-31. It has since remained available on npm for 1575 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.
v0.14.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-03-22. It has since remained available on npm for 1584 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.
v0.14.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-03-21. It has since remained available on npm for 1585 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.
v0.13.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2022-01-05. It has since remained available on npm for 1661 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.
v0.13.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-12-27. It has since remained available on npm for 1669 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.
v0.12.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-11-22. It has since remained available on npm for 1704 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.
v0.12.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-10-28. It has since remained available on npm for 1730 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.
v0.11.3
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-09-24. It has since remained available on npm for 1763 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.
v0.11.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-09-08. It has since remained available on npm for 1779 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.
v0.11.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-08-25. It has since remained available on npm for 1793 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.
v0.11.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-08-25. It has since remained available on npm for 1793 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.
v0.10.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-06-19. It has since remained available on npm for 1860 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.
v0.9.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-26. It has since remained available on npm for 1884 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.
v0.9.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-25. It has since remained available on npm for 1885 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.
v0.8.4
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-06. It has since remained available on npm for 1904 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.
v0.8.3
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-05. It has since remained available on npm for 1905 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.
v0.8.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-05. It has since remained available on npm for 1905 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.
v0.8.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-05. It has since remained available on npm for 1905 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.
v0.8.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-05-05. It has since remained available on npm for 1906 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.
v0.7.5
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-28. It has since remained available on npm for 1912 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.
v0.7.4
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-27. It has since remained available on npm for 1913 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.
v0.7.3
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-21. It has since remained available on npm for 1919 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.
v0.7.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-19. It has since remained available on npm for 1921 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.
v0.7.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-19. It has since remained available on npm for 1921 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.
v0.7.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-15. It has since remained available on npm for 1925 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.
v0.6.2
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-04-05. It has since remained available on npm for 1935 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.
v0.6.1
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-03-30. It has since remained available on npm for 1942 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.
v0.6.0
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2021-03-22. It has since remained available on npm for 1950 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.
v0.3.5
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2020-12-21. It has since remained available on npm for 2040 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.
v0.3.4
2 findingsThis version was published by a different npm account (hasparus) than the most recent previously approved version (jxnblk) on 2020-11-20. It has since remained available on npm for 2071 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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.