@zuplo/errors
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from zuplo-integrations to GitHub Actions, consistent with a CI/CD migration for the @zuplo org. Scoped package under a registered npm org reduces takeover risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer moritzs is consistent with a legitimate Zuplo org contributor addition. Scoped @zuplo package limits unauthorized additions. | ai |
Versions (showing 45 of 548)
| Version | Deps | Published |
|---|---|---|
| 6.51.23 | 0 / 6 | |
| 6.51.22 | 0 / 6 | |
| 6.51.21 | 0 / 6 | |
| 6.51.20 | 0 / 6 | |
| 6.51.19 | 0 / 6 | |
| 6.51.17 | 0 / 6 | |
| 6.51.16 | 0 / 6 | |
| 6.51.15 | 0 / 6 | |
| 6.51.14 | 0 / 6 | |
| 6.51.13 | 0 / 6 | |
| 6.51.12 | 0 / 6 | |
| 6.51.11 | 0 / 6 | |
| 6.51.10 | 0 / 6 | |
| 6.51.9 | 0 / 6 | |
| 6.51.7 | 0 / 6 | |
| 6.51.6 | 0 / 6 | |
| 6.51.5 | 0 / 6 | |
| 6.51.4 | 0 / 6 | |
| 6.51.3 | 0 / 6 | |
| 6.51.2 | 0 / 6 | |
| 6.51.1 | 0 / 6 | |
| 6.51.0 | 0 / 6 | |
| 6.50.16 | 0 / 6 | |
| 6.50.14 | 0 / 6 | |
| 6.50.13 | 0 / 6 | |
| 6.50.12 | 0 / 6 | |
| 6.50.11 | 0 / 6 | |
| 6.50.10 | 0 / 6 | |
| 6.50.9 | 0 / 6 | |
| 6.50.8 | 0 / 6 | |
| 6.50.7 | 0 / 6 | |
| 6.50.6 | 0 / 6 | |
| 6.50.5 | 0 / 6 | |
| 6.50.4 | 0 / 6 | |
| 6.50.2 | 0 / 6 | |
| 6.50.1 | 0 / 6 | |
| 6.50.0 | 0 / 6 | |
| 6.49.12 | 0 / 6 | |
| 6.49.11 | 0 / 6 | |
| 6.49.9 | 0 / 6 | |
| 6.49.8 | 0 / 6 | |
| 6.49.7 | 0 / 6 | |
| 6.49.6 | 0 / 6 | |
| 6.49.5 | 0 / 6 | |
| 6.49.4 | 0 / 6 |
v6.51.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.51.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.51.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.51.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.