@pareto-engineering/assets
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher moved to CI/CD (GitHub Actions), consistent with legitimate automated release pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are pareto.engineering employees; consistent with internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers match added ones in pattern; team transition, no behavior change in diff. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 5.14.4 | 0 / 0 | |
| 5.14.3 | 0 / 0 | |
| 5.12.20 | 0 / 0 | |
| 5.12.19 | 0 / 0 | |
| 5.12.18 | 0 / 0 | |
| 5.12.17 | 0 / 0 | |
| 5.12.16 | 0 / 0 | |
| 5.12.15 | 0 / 0 | |
| 5.12.14 | 0 / 0 | |
| 5.12.12 | 0 / 0 | |
| 5.12.11 | 0 / 0 | |
| 5.12.10 | 0 / 0 | |
| 5.12.9 | 0 / 0 | |
| 5.12.8 | 0 / 0 | |
| 5.12.7 | 0 / 0 | |
| 5.12.6 | 0 / 0 | |
| 5.12.5 | 0 / 0 | |
| 5.12.4 | 0 / 0 | |
| 5.12.2 | 0 / 0 | |
| 5.12.1 | 0 / 0 | |
| 5.12.0 | 0 / 0 | |
| 5.11.24 | 0 / 0 | |
| 5.11.23 | 0 / 0 | |
| 5.11.22 | 0 / 0 | |
| 5.11.21 | 0 / 0 | |
| 5.11.20 | 0 / 0 | |
| 5.11.19 | 0 / 0 | |
| 5.11.18 | 0 / 0 | |
| 5.11.17 | 0 / 0 | |
| 5.11.16 | 0 / 0 | |
| 5.11.5 | 0 / 0 | |
| 5.11.4 | 0 / 0 | |
| 5.11.3 | 0 / 0 | |
| 5.11.2 | 0 / 0 | |
| 5.11.1 | 0 / 0 | |
| 5.11.0 | 0 / 0 | |
| 5.10.4 | 0 / 0 | |
| 5.10.3 | 0 / 0 | |
| 5.10.2 | 0 / 0 | |
| 5.10.1 | 0 / 0 | |
| 5.10.0 | 0 / 0 | |
| 5.9.0 | 0 / 0 | |
| 5.8.0 | 0 / 0 | |
| 5.7.0 | 0 / 0 | |
| 5.6.0 | 0 / 0 | |
| 5.5.0 | 0 / 0 | |
| 5.4.0 | 0 / 0 | |
| 5.3.0 | 0 / 0 | |
| 5.1.1 | 0 / 0 | |
| 5.1.0 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.14.4
2 findingsThis version was published by a different npm account than previous versions on 2026-07-23. 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.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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.