@pareto-engineering/bem
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Internal org maintainer reshuffle, no behavior change in package contents. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with additions from same org; no takeover indicators in diff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic internal design package; dormancy expected, no malicious diff. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 5.14.4 | 0 / 5 | |
| 5.14.3 | 0 / 5 | |
| 5.11.5 | 0 / 5 | |
| 5.11.4 | 0 / 5 | |
| 5.11.3 | 0 / 5 | |
| 5.11.2 | 0 / 5 | |
| 5.11.1 | 0 / 5 | |
| 5.11.0 | 0 / 5 | |
| 5.10.4 | 0 / 5 | |
| 5.10.3 | 0 / 5 | |
| 5.10.2 | 0 / 5 | |
| 5.10.1 | 0 / 5 | |
| 5.10.0 | 0 / 5 | |
| 5.9.0 | 0 / 5 | |
| 5.8.0 | 0 / 5 | |
| 5.7.0 | 0 / 5 | |
| 5.6.0 | 0 / 5 | |
| 5.5.0 | 0 / 5 | |
| 5.4.0 | 0 / 5 | |
| 5.3.0 | 0 / 5 | |
| 5.2.1 | 0 / 5 | |
| 5.0.0 | 0 / 5 |
v5.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.