@epilot/automation-client
Client library for epilot automation API
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): Well-known DAZN Lambda powertools library; stable dependency across epilot SDK versions. | ai | |
| provenance | no-provenance | AI (provenance): Established epilot SDK package; no provenance is consistent across all 185 versions. | ai | |
| provenance | publisher-changed | AI (provenance): daniel-bot.epilot is an epilot org bot with 12 approved packages; publisher change reflects org CI/CD transition, not compromise. | ai | |
| phantom-deps | phantom-dep:stream-http | AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import. | ai | |
| phantom-deps | phantom-dep:https-browserify | AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 2.33.4 | 5 / 14 | |
| 2.33.3 | 5 / 14 | |
| 2.33.2 | 5 / 14 | |
| 2.33.1 | 5 / 14 | |
| 2.33.0 | 5 / 14 | |
| 2.32.0 | 5 / 14 | |
| 2.31.0 | 5 / 14 | |
| 2.30.0 | 5 / 14 | |
| 2.29.0 | 5 / 17 | |
| 2.28.0 | 5 / 17 | |
| 2.27.0 | 5 / 17 | |
| 2.26.0 | 5 / 17 | |
| 2.25.0 | 5 / 17 | |
| 2.24.3 | 5 / 17 | |
| 2.24.2 | 5 / 17 | |
| 2.24.1 | 5 / 17 | |
| 2.24.0 | 5 / 17 | |
| 2.23.0 | 5 / 17 | |
| 2.22.5 | 5 / 17 | |
| 2.22.4 | 5 / 17 | |
| 2.22.3 | 5 / 17 | |
| 2.22.2 | 5 / 17 | |
| 2.22.1 | 5 / 17 | |
| 2.22.0 | 5 / 17 | |
| 2.21.0 | 6 / 17 | |
| 2.19.3 | 5 / 17 | |
| 2.19.2 | 5 / 17 | |
| 2.19.1 | 5 / 17 | |
| 2.19.0 | 6 / 17 | |
| 2.18.9 | 5 / 17 | |
| 2.18.8 | 5 / 17 | |
| 2.18.7 | 5 / 17 | |
| 2.17.3 | 6 / 17 | |
| 2.17.2 | 6 / 17 | |
| 2.17.0 | 6 / 17 | |
| 2.16.5 | 6 / 17 | |
| 2.16.4 | 6 / 17 | |
| 2.16.2 | 6 / 17 | |
| 2.16.1 | 6 / 17 | |
| 2.16.0 | 6 / 17 | |
| 2.15.1 | 6 / 17 | |
| 2.15.0 | 6 / 17 | |
| 2.14.10 | 6 / 17 | |
| 2.14.9 | 6 / 17 | |
| 2.14.8 | 6 / 17 | |
| 2.14.7 | 6 / 17 | |
| 2.14.6 | 6 / 17 | |
| 2.14.5 | 6 / 17 | |
| 2.14.4 | 6 / 17 | |
| 2.14.3 | 6 / 17 | |
| 2.14.2 | 6 / 17 |
v2.16.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 (sumanth.kanakala) than the most recent previously approved version (sebas.sauer) on 2025-04-16, but sumanth.kanakala 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.
v2.16.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 (sebas.sauer) than the most recent previously approved version (epilot-dev-tools) on 2025-04-11, but sebas.sauer 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.
v2.16.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 (epilot-dev-tools) than the most recent previously approved version (sebas.sauer) on 2025-04-11, but epilot-dev-tools 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.
v2.16.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 (sebas.sauer) than the most recent previously approved version (jakub.duras.epilot) on 2025-04-08, but sebas.sauer 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.
v2.16.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 (sebas.sauer) than the most recent previously approved version (jakub.duras.epilot) on 2025-04-08, but sebas.sauer 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.
v2.15.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 (jakub.duras.epilot) than the most recent previously approved version (dusty48) on 2025-02-27, but jakub.duras.epilot 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.
v2.15.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 (jakub.duras.epilot) than the most recent previously approved version (dusty48) on 2025-02-27, but jakub.duras.epilot 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.
v2.14.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 (dusty48) than the most recent previously approved version (sumanth.kanakala) on 2025-02-04, but dusty48 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.
v2.14.9
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 (dusty48) than the most recent previously approved version (sumanth.kanakala) on 2025-02-04, but dusty48 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.
v2.14.8
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 (sumanth.kanakala) than the most recent previously approved version (vladcrishan) on 2024-12-24, but sumanth.kanakala 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.
v2.14.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.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 (vladcrishan) than the most recent previously approved version (epilot-dev-tools) on 2024-11-03, but vladcrishan 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.