@panneau/display-badges
Colored badges
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:react-intl | AI (phantom-deps): react-intl is a declared peer/dep used transitively in this UI component; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@panneau/core | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on monorepo packages that re-export rather than directly import. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.0.56 | 6 / 2 | |
| 4.0.55 | 6 / 2 | |
| 4.0.50 | 6 / 2 | |
| 4.0.48 | 6 / 2 | |
| 4.0.41 | 6 / 2 | |
| 4.0.39 | 6 / 2 | |
| 4.0.27 | 6 / 2 | |
| 4.0.21 | 6 / 2 | |
| 4.0.18 | 6 / 2 | |
| 4.0.17 | 6 / 2 | |
| 4.0.8 | 7 / 2 | |
| 4.0.7 | 7 / 2 | |
| 4.0.6 | 7 / 2 | |
| 4.0.5 | 7 / 2 | |
| 4.0.4 | 7 / 2 | |
| 4.0.2 | 7 / 2 | |
| 4.0.1 | 7 / 2 | |
| 4.0.0 | 7 / 2 | |
| 3.0.314 | 7 / 2 | |
| 3.0.307 | 7 / 2 |
v4.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.39
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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
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. Consider requesting the maintainer enable provenance via CI/CD.
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.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.