@panneau/app
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:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dependency; stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with clear purpose; empty description is benign here. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a common React peer/config dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): FontAwesome deps declared for config/re-export; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): FontAwesome deps declared for config/re-export; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@folklore/routes | AI (dependencies): Same org (@folklore) as the package publisher; consistent across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@panneau/element-grid | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-icon | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-range | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-avatar | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-radios | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-buttons | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-accordion | AI (phantom-deps): Same monorepo pattern. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @panneau/app; Levenshtein distance to unrelated single-word packages is meaningless noise. | ai | |
| phantom-deps | phantom-dep:@panneau/element-media-card | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-pagination | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-breadcrumbs | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-media-player | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@fortawesome/react-fontawesome | AI (phantom-deps): Config-file reference in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@panneau/element-resource-card | AI (phantom-deps): Same monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@panneau/element-form-group | AI (phantom-deps): Same monorepo pattern. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same as above — scoped monorepo package, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same as above — scoped monorepo package, not a typosquat of 'yup'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same as above — scoped monorepo package, not a typosquat of 'ajv'. | ai | |
| phantom-deps | phantom-dep:@panneau/themes | AI (phantom-deps): Monorepo umbrella package; same-org deps may be re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@panneau/element-form | AI (phantom-deps): Same monorepo pattern. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 4.0.55 | 49 / 2 | |
| 4.0.52 | 49 / 2 | |
| 4.0.50 | 49 / 2 | |
| 4.0.49 | 49 / 2 | |
| 4.0.48 | 49 / 2 | |
| 4.0.46 | 49 / 2 | |
| 4.0.45 | 49 / 2 | |
| 4.0.41 | 49 / 2 | |
| 4.0.39 | 49 / 2 | |
| 4.0.38 | 49 / 2 | |
| 4.0.37 | 49 / 2 | |
| 4.0.34 | 49 / 2 | |
| 4.0.33 | 49 / 2 | |
| 4.0.32 | 49 / 2 | |
| 4.0.31 | 49 / 2 | |
| 4.0.28 | 49 / 2 | |
| 4.0.27 | 49 / 2 | |
| 4.0.26 | 49 / 2 | |
| 4.0.24 | 49 / 2 | |
| 4.0.23 | 49 / 2 | |
| 4.0.21 | 49 / 2 | |
| 4.0.20 | 49 / 2 | |
| 4.0.19 | 49 / 2 | |
| 4.0.18 | 49 / 2 | |
| 4.0.17 | 49 / 2 | |
| 4.0.15 | 49 / 2 | |
| 4.0.14 | 49 / 2 | |
| 4.0.11 | 50 / 2 | |
| 4.0.8 | 50 / 2 | |
| 4.0.7 | 50 / 2 | |
| 4.0.6 | 50 / 2 | |
| 4.0.5 | 50 / 2 | |
| 4.0.4 | 50 / 2 | |
| 4.0.3 | 50 / 2 | |
| 4.0.2 | 50 / 2 | |
| 4.0.1 | 50 / 2 | |
| 4.0.0 | 50 / 2 | |
| 3.0.323 | 50 / 2 | |
| 3.0.322 | 50 / 2 | |
| 3.0.321 | 50 / 2 | |
| 3.0.319 | 50 / 2 | |
| 3.0.317 | 50 / 2 | |
| 3.0.315 | 50 / 2 | |
| 3.0.314 | 50 / 2 | |
| 3.0.313 | 50 / 2 | |
| 3.0.312 | 50 / 2 | |
| 3.0.311 | 50 / 2 | |
| 3.0.310 | 50 / 2 | |
| 3.0.309 | 50 / 2 | |
| 3.0.308 | 50 / 2 | |
| 3.0.307 | 50 / 2 |
v4.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.52
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.49
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.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.45
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.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.38
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2026-04-29, but dmongeau 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.
v4.0.37
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 (dmongeau) than the most recent previously approved version (phatshambler) on 2026-04-29, but dmongeau 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.
v4.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.323
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.322
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.321
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. Consider requesting the maintainer enable provenance via CI/CD.
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.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.313
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.311
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.310
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.309
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.