@tanglydocs/theme-ui
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:astro | AI (phantom-deps): Config-referenced dependency; stable pattern for Astro theme packages. | ai | |
| phantom-deps | phantom-dep:katex | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:lucide | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:mermaid | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:@astrojs/mdx | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:remark-rehype | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:rehype-sanitize | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:rehype-stringify | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/vite | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai | |
| phantom-deps | phantom-dep:@tanglydocs/schema | AI (phantom-deps): Same-org dependency; stable pattern for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@scalar/api-reference | AI (phantom-deps): Config-referenced dependency; stable pattern for theme packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 22 / 2 | |
| 0.1.4 | 22 / 2 | |
| 0.1.3 | 22 / 2 | |
| 0.1.2 | 22 / 2 | |
| 0.1.0 | 22 / 2 | |
| 0.0.12 | 22 / 2 | |
| 0.0.11 | 22 / 2 | |
| 0.0.10 | 22 / 2 | |
| 0.0.9 | 22 / 2 | |
| 0.0.8 | 16 / 1 | |
| 0.0.6 | 16 / 1 | |
| 0.0.5 | 16 / 1 | |
| 0.0.4 | 16 / 1 | |
| 0.0.3 | 16 / 1 | |
| 0.0.2 | 16 / 1 |
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.