← Home

@epilot/pricing

npm Repository Homepage

Pricing Library

37
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

daniel-bot.epilotsumanth.kanakalajulian01sdrdhanttiviljamij.pinhopraneetrosureshkumarsa.kediasebas.sauerepilot-dev-toolsalexmarqsvladcrishanwmolinarij.carneironishugoeljakub.duras.epilotjulian.maurermanikandan.subramanianberni-epilotmateus.nardogokul.kalaikovan.epilotkarl.epilotpriit.parnathisisernestoepilot.ernestomarta-osowieckaepilot-blomqmagabriel.epilothelyaepilotflavius_amsergey.sedelnikov.epilotdanuta.ludwikowskaajamuar_epilotluca-felix-epilots.tothmarta.pestkafriedrich_epilotbalintk-epilotankit.prasadkshitij.saxena.epilotpaulo.henriquesniko.kozivjosh.stewart.epilotjoecaseepilotrichard.griffithsflorian.fuchs.epilotsimone.epilot

Keywords

pricing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both publishers are within the epilot org; alexmarqs has 44 approved packages and no hostile indicators. ai
publish-pattern dormant-publish AI (publish-pattern): Established epilot org package; no material changes from prior version; publisher has strong approval track record. ai
dependencies unvetted-dep:dinero.js AI (dependencies): dinero.js is a well-known currency library; stable legitimate dependency for a pricing package. ai
license uncommon-license:UNLICENSED AI (license): Proprietary epilot org package; UNLICENSED is intentional and consistent across versions. ai

Versions (showing 37 of 37)

Version Deps Published
5.6.7 1 / 17
5.6.6 1 / 17
5.6.2 1 / 17
5.6.1 1 / 16
5.6.0 1 / 16
5.3.7 1 / 16
5.3.6 1 / 16
5.3.5 1 / 16
5.3.4 1 / 16
5.3.2 1 / 16
5.3.1 1 / 16
5.3.0 1 / 16
5.2.8 1 / 16
5.2.7 1 / 16
5.2.6 1 / 16
5.2.5 1 / 16
5.2.4 1 / 16
5.2.3 1 / 16
5.2.2 1 / 16
5.2.1 1 / 16
5.2.0 1 / 16
5.1.8 1 / 16
5.1.7 1 / 16
5.1.6 1 / 16
5.1.5 1 / 16
5.1.4 1 / 16
5.1.3 1 / 16
5.1.2 1 / 16
5.1.1 1 / 16
5.1.0 1 / 16
5.0.8 1 / 16
5.0.5 1 / 16
5.0.4 1 / 16
5.0.3 1 / 16
5.0.2 1 / 16
5.0.1 1 / 16
5.0.0 1 / 16

v5.6.7

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: epilot-dev-tools.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.3.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.2.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.2.6

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-09-25) provenance

This version was published by a different npm account than previous versions on 2025-09-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.5

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-09-02) provenance

This version was published by a different npm account than previous versions on 2025-09-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.4

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-29) provenance

This version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.3

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-29) provenance

This version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.2

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-28) provenance

This version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.1

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-27) provenance

This version was published by a different npm account than previous versions on 2025-08-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

2 findings
HIGH Publisher changed: j.carneiro → diogo.f.marques (on 2025-08-26) provenance

This version was published by a different npm account than previous versions on 2025-08-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.8

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-21) provenance

This version was published by a different npm account than previous versions on 2025-08-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.7

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-19) provenance

This version was published by a different npm account than previous versions on 2025-08-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.6

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-15) provenance

This version was published by a different npm account than previous versions on 2025-08-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.5

2 findings
HIGH Publisher changed: j.carneiro → diogo.f.marques (on 2025-08-06) provenance

This version was published by a different npm account than previous versions on 2025-08-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.4

2 findings
HIGH Publisher changed: j.carneiro → diogo.f.marques (on 2025-08-06) provenance

This version was published by a different npm account than previous versions on 2025-08-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.3

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-08-04) provenance

This version was published by a different npm account than previous versions on 2025-08-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.2

2 findings
HIGH Publisher changed: j.carneiro → paulo.henriques (on 2025-07-30) provenance

This version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.1

2 findings
HIGH Publisher changed: j.carneiro → paulo.henriques (on 2025-07-30) provenance

This version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

2 findings
HIGH Publisher changed: j.carneiro → paulo.henriques (on 2025-07-30) provenance

This version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.8

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-07-29) provenance

This version was published by a different npm account than previous versions on 2025-07-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.5

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-06-05) provenance

This version was published by a different npm account than previous versions on 2025-06-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.4

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-05-26) provenance

This version was published by a different npm account than previous versions on 2025-05-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.3

2 findings
HIGH Publisher changed: j.carneiro → alexmarqs (on 2025-05-26) provenance

This version was published by a different npm account than previous versions on 2025-05-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.