@panneau/element-portal
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:prop-types | AI (phantom-deps): Runtime dependency for React component prop validation; stable pattern. | ai | |
| phantom-deps | phantom-dep:react-intl | AI (phantom-deps): Runtime dependency for i18n in React components; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Standard Babel convention dependency; stable across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.41 | 2 / 2 | |
| 4.0.38 | 2 / 2 | |
| 4.0.37 | 2 / 2 | |
| 4.0.14 | 2 / 2 | |
| 4.0.11 | 3 / 2 | |
| 4.0.5 | 3 / 2 | |
| 4.0.2 | 3 / 2 | |
| 4.0.0 | 3 / 2 | |
| 3.0.319 | 3 / 2 | |
| 3.0.317 | 3 / 2 |
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
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.2
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. 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.