← Home

@aptos-scp/isl-types-integration

npm Repository Homepage

Type definitions and schemas for Integration Service Layer (ISL)

45
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mraoaptosaly-aptos-comsfrederick3anshu.sharmanapoleonlazoaptosrjeyapaul-aptos-comranjan.mishraaptosarajoria-aptos-comadoppalapudi-aptos-commahendraborchate-aptos-comhrobieaptoslabsbgillaptspringciwanderson-aptosmscandoloprabhuramesh-aptos-comkevinrobertsonaptosuhernandezaptoscapstone-isjmeyersjcampanellaazhytkevichaptoselendofmjonessshikharrgrigoroiumpajukggeorge-aptos-comsapatelanilkumarsinghaptosamercednkeaneyajholztjohnsonaptoskvlogiannitiswwilkieaptosidimitrovaptosjgalanakisrnsavagebalavitruviusdipan68pvenukumarsmandalsnagarajdcosletjespinozaaptosfernandeznfmartinez-aptos-comaptos-apinedaydingaptosstevenbouchardaptosone_npmmvgeeteruyenlramirezaptoshkuttipuravanrmartinezaptosanilkumar.reddymvenkatarajuakhoukazmstoneraptossallipurgmyers-aptosagawarergoel-aptos-commgondhalkar-aptos-comrrudrakanthwar-aptos-compkushwaha-aptos-comskeaneyaptosdhughesaptosbmclaughlinaptosaajayan-aptos-comaperiyasamy-aptos-comjloginaptoscuptonaptosasoni-aptos-comccepbkulichaptosjbrennanaptosgkaurrorocaptosaptosjguillemetteamitkumaraptosrjayantiaptosrevanasiddaptosvpakanati-aptos-combkansara-aptos-comoblevinsaptosmkulichaptosawongaptosprapanna.mondalabharadwajaptosddelsavioaptosdburroughsaptosgriveriniperezaptosmedwardsaptosnandan-aptos-comaptosalakmalalit.puriaptosalexhensonaptosdjain-aptos-comapangburnaptosrjburton63yogeshdahake-aptos-comswangaptosrmadgundi-aptos-comssethumadhavan-aptosgordongillespieaptosibhaskaranaptosmahmedaptoslmerrittdskripnikovaptosrathnabm-aptos-comcharishma.chandrakumarshobhitsinghaptosogonzalezaptoschetansbaptosasutoshpandaaptosdev.infradhruvabaptosbsheppardmatsuoaptoschallakarthikaptosvpawar-aptos-combkumar-aptos-comgautamhrishikeshaptosvishnu.rajawat.aptosshivindrakantiaptosagiridhar-aptos-comdianovaleaptossreddyaptosjvyasmlmcintoshaptossaifialiaptossukritibahriaptoscharles.dupeeritugowdaaptosrparthasarathyigordonnickkayurovaptosbwongaptosmanikandanpaptosasurya-aptos-comachapaitkar-aptos-comaarathi.varshadabdulaptosadityapotdaraptosnarendra.rpkadlikoppa-aptos-comsanjanabanothaptosrisharorasaravanantaptosrahulshettyaptosamanjakharaptosramyasaptosmahesh.annavarapuvkhilnaniaptosarchanahuckavathekartheamoghpalbdas-aptos-comanjalikumariaptosamohanishgeetanshmamtaniaptosnvani-aptos-comlyndonpuzonaptosmohitgahlotaptosavigyan-bhakta-aptos-comammatteplozano_aptosrujoolpatilaptosfsalaicesmark.baker-aptos-comsperkinsaptosluke.tibbetts-aptos-comnithyarvaptoshtsiolisshishiraptoskkuber-aptos-comkanimozhithangavelaptosvinaykarnatiaptosaruna.mathaptosernest.crastoaptossanikaamaptosjvalan-aptos-commdeshpande-aptos-comjithu-s-aptos-comhgupta-aptos-comsanjanabt-aptos-comkasettysailesh-aptos-comamoghpalelozanoaptossakshamaptoskumarharshaptoskhushi-sharma-aptos-comayushpandeyaptosyukthamaptosvenkateshtadikamallaaptosniveditatiwariaptosjstrohlmanasshahaptosabhilashmishra-aptos-comtalarcon1mayankajainaptosnperumal-aptosssahoo-aptos-comrohanshettyaptoscsuraboyna-aptos-comshreyasinhaaptoskyle-thompson-aptosmichael.kacerpuneetdewanaptosankumaraptosrob-johnson-aptos-comharshwardhansolankiaptossantoshkoganoleaptosksinghaptoslata-rawal-aptos-comnaveenaptossumalikabodeddula-aptos-comdavid-baxendale-aptos-comishani.chaudhuriaptosvishnunc-aptossimonrowlandaptosramyakalal-aptos-comgaurav-pratap-aptos-compulkit-yadav-aptos-compramodp-aptos-comaaugustine-aptos-comksowndaryadeepukumaraptosgopalprasadaptosaryan-kashyap-aptos-com

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Type-definitions package from established org; no provenance is common and not a risk here. ai
email-domain unclaimed-email:y.com AI (email-domain): [email protected] is a placeholder email; package is an established type-definitions library with 44 versions and a legitimate org repo. ai

Versions (showing 45 of 45)

Version Deps Published
1.33.0 0 / 44
1.32.1 0 / 44
1.31.2 0 / 44
1.31.1 0 / 44
1.31.0 0 / 44
1.30.0 0 / 44
1.29.0 0 / 44
1.28.1 0 / 44
1.28.0 0 / 44
1.27.0 0 / 44
1.26.0 0 / 44
1.25.0 0 / 44
1.24.0 0 / 44
1.23.1 0 / 44
1.23.0 0 / 44
1.22.0 0 / 44
1.21.1 0 / 44
1.20.2 0 / 44
1.20.1 0 / 44
1.20.0 0 / 44
1.19.0 0 / 44
1.18.0 0 / 44
1.17.0 0 / 44
1.16.0 0 / 44
1.15.0 0 / 44
1.14.0 0 / 44
1.13.3 0 / 44
1.13.2 0 / 43
1.13.1 0 / 43
1.11.1 0 / 43
1.11.0 0 / 43
1.10.0 0 / 43
1.9.0 0 / 43
1.8.0 0 / 43
1.7.0 0 / 43
1.6.0 0 / 43
1.5.1 0 / 43
1.5.0 0 / 43
1.4.0 0 / 43
1.3.1 0 / 43
1.3.0 0 / 43
1.2.0 0 / 43
1.1.0 0 / 43
1.0.1 0 / 43
1.0.0 0 / 43

v1.33.0

1 finding
INFO No provenance attestation provenance

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

v1.32.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.31.2

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.31.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.31.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.30.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.29.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.28.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.28.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.27.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.26.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.25.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.24.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.23.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.23.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.22.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.21.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.20.2

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.20.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.20.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.19.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.18.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.17.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.16.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.15.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.14.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.13.3

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.13.2

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.13.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.11.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.11.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.10.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.9.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.8.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.7.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.6.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.5.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.5.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.4.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.3.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.3.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.2.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.1.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.0.1

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v1.0.0

2 findings
HIGH Unclaimed maintainer email domain: y.com email-domain

Maintainer email '[email protected]' uses domain 'y.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.