@panneau/themes
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:lodash-es | AI (phantom-deps): Config-referenced utility; stable pattern for this theme package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Config-referenced utility; stable pattern for this theme package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Likely used in bundled output or config; stable false positive for this themes package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): CSS/config-level usage in a themes package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@panneau/core | AI (phantom-deps): Same-org sibling dep; phantom detection is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:bootstrap | AI (phantom-deps): Bootstrap is a CSS dependency consumed via styles, not JS imports; stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 5 / 2 | |
| 4.0.50 | 5 / 2 | |
| 4.0.48 | 5 / 2 | |
| 4.0.41 | 5 / 2 | |
| 4.0.38 | 5 / 2 | |
| 4.0.37 | 5 / 2 | |
| 4.0.36 | 5 / 2 | |
| 4.0.34 | 5 / 2 | |
| 4.0.33 | 5 / 2 | |
| 4.0.15 | 5 / 2 | |
| 4.0.14 | 5 / 2 | |
| 4.0.11 | 6 / 2 | |
| 4.0.8 | 6 / 2 | |
| 4.0.7 | 6 / 2 | |
| 4.0.6 | 6 / 2 | |
| 4.0.5 | 6 / 2 | |
| 4.0.4 | 6 / 2 | |
| 4.0.2 | 6 / 2 | |
| 4.0.1 | 6 / 2 | |
| 4.0.0 | 6 / 2 | |
| 3.0.319 | 6 / 2 | |
| 3.0.317 | 6 / 2 | |
| 3.0.314 | 6 / 2 | |
| 3.0.308 | 6 / 2 | |
| 3.0.307 | 6 / 2 |
v4.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.319
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.