@jitsu/functions-lib
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD publisher via GitHub Actions with SLSA attestation, an improvement over manual publish. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with legitimate org maintainer addition alongside CI provenance switch. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.14.0 | 0 / 10 | |
| 1.10.4 | 0 / 11 | |
| 1.10.3 | 0 / 11 | |
| 1.10.2 | 0 / 11 | |
| 1.10.1 | 0 / 11 | |
| 1.10.0 | 0 / 11 | |
| 1.9.17 | 0 / 11 | |
| 1.9.15 | 0 / 11 | |
| 1.9.14 | 0 / 11 | |
| 1.9.13 | 0 / 11 |
v2.14.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.