@epilot/pricing-client
Client for epilot Pricing APIs
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dazn/lambda-powertools-correlation-ids | AI (dependencies): Known AWS Lambda observability library from DAZN; stable legitimate dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established epilot SDK package; lack of provenance is consistent across all 266 versions and is not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Node.js polyfill for browser bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): Node.js polyfill for browser bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:https-browserify | AI (phantom-deps): Node.js polyfill for browser bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stream-http | AI (phantom-deps): Node.js polyfill for browser bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Node.js polyfill for browser bundle; stable pattern for this package. | ai |
Versions (showing 51 of 139)
| Version | Deps | Published |
|---|---|---|
| 3.54.3 | 7 / 9 | |
| 3.54.2 | 7 / 9 | |
| 3.54.1 | 7 / 9 | |
| 3.54.0 | 7 / 9 | |
| 3.53.7 | 7 / 9 | |
| 3.53.6 | 7 / 9 | |
| 3.51.0 | 7 / 12 | |
| 3.47.7 | 7 / 12 | |
| 3.47.6 | 7 / 12 | |
| 3.47.5 | 7 / 12 | |
| 3.47.4 | 7 / 12 | |
| 3.47.3 | 7 / 12 | |
| 3.47.2 | 7 / 12 | |
| 3.47.1 | 7 / 12 | |
| 3.47.0 | 7 / 12 | |
| 3.46.1 | 7 / 12 | |
| 3.46.0 | 7 / 12 | |
| 3.45.0 | 7 / 12 | |
| 3.44.0 | 7 / 12 | |
| 3.43.0 | 7 / 12 | |
| 3.42.0 | 7 / 12 | |
| 3.41.0 | 7 / 12 | |
| 3.40.0 | 7 / 12 | |
| 3.39.0 | 7 / 12 | |
| 3.38.0 | 7 / 12 | |
| 3.37.0 | 7 / 12 | |
| 3.36.7 | 7 / 12 | |
| 3.36.6 | 7 / 12 | |
| 3.36.5 | 7 / 12 | |
| 3.36.4 | 7 / 12 | |
| 3.36.3 | 7 / 12 | |
| 3.36.2 | 7 / 12 | |
| 3.36.1 | 7 / 12 | |
| 3.36.0 | 7 / 12 | |
| 3.35.17 | 7 / 12 | |
| 3.35.16 | 7 / 12 | |
| 3.35.15 | 7 / 12 | |
| 3.35.14 | 7 / 12 | |
| 3.35.13 | 7 / 12 | |
| 3.35.12 | 7 / 12 | |
| 3.35.11 | 7 / 12 | |
| 3.35.10 | 7 / 12 | |
| 3.35.9 | 7 / 12 | |
| 3.35.8 | 7 / 12 | |
| 3.35.7 | 7 / 12 | |
| 3.35.6 | 7 / 12 | |
| 3.35.5 | 7 / 12 | |
| 3.35.4 | 7 / 12 | |
| 3.35.3 | 7 / 12 | |
| 3.35.2 | 7 / 12 | |
| 3.35.1 | 7 / 12 |
v3.47.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (diogo.f.marques) than the most recent previously approved version (priit.parna) on 2025-04-16, but diogo.f.marques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.47.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (priit.parna) than the most recent previously approved version (paulo.henriques) on 2025-04-16, but priit.parna is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.47.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (paulo.henriques) on 2025-03-19, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.47.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (alexmarqs) on 2025-03-06, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.47.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (alexmarqs) on 2025-03-06, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (alexmarqs) on 2025-02-27, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.46.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2025-02-25, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.44.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (j.carneiro) on 2025-02-12, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.42.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (julian.maurer) than the most recent previously approved version (j.carneiro) on 2025-02-04, but julian.maurer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (julian.maurer) on 2025-01-29, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.37.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (julian.maurer) than the most recent previously approved version (alexmarqs) on 2025-01-28, but julian.maurer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2025-01-20, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (alexmarqs) on 2025-01-20, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2025-01-20, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (paulo.henriques) on 2025-01-10, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (paulo.henriques) on 2024-12-06, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (diogo.f.marques) on 2024-12-03, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.36.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paulo.henriques) than the most recent previously approved version (diogo.f.marques) on 2024-12-03, but paulo.henriques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (diogo.f.marques) than the most recent previously approved version (j.carneiro) on 2024-11-19, but diogo.f.marques is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2024-11-18, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (alexmarqs) on 2024-11-18, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (alexmarqs) on 2024-11-18, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2024-11-13, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2024-11-05, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (j.carneiro) than the most recent previously approved version (alexmarqs) on 2024-10-31, but j.carneiro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.35.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexmarqs) than the most recent previously approved version (j.carneiro) on 2024-10-16, but alexmarqs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.