@oat-sa/tao-item-runner-qti GPL-2.0 48 versions

@oat-sa/tao-item-runner-qti

npm Repository Homepage

TAO QTI Item Runner modules

48

Versions

GPL-2.0

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jsconanoatymartoat-adminshavekokilatibwazelinmarpesiagauravoatyukipastelcatgloribeloatviktar_dzmitryieugabriel-taoolga-kulish-taouncleemptysabatkeshelashvilijuan.vazquez.taokirill.gatalskytikhanovichllecaqueshpranpribim.aleknaviciuspkorczaktaoroma-derskiebersolejimangasandresmoranjulia-klementowicz-taoar0oattstankeviciusmathusalim-orgrjtg1992pedro.marce-rodriguezsergio-taoykfeoatalxjenetalejandro-luengo-taotestinganna-llorenspeetyaluis-murciano-taoaleksej-tikhanovichkarolsarcadiuszpiczakgustavo.molitordriule

Keywords

taoitemrunnerqtifefrontend

Versions (showing 48 of 48)

Version	Deps	Published
2.11.0	0 / 41	2026-07-03
2.10.8	0 / 41	2026-06-15
2.10.6	0 / 41	2026-04-02
2.10.5	0 / 41	2026-03-30
2.10.4	0 / 41	2026-03-19
2.10.3	0 / 41	2026-03-11
2.10.2	0 / 41	2026-02-20
2.10.1	0 / 41	2026-02-06
2.10.0	0 / 41	2026-02-05
2.9.0	0 / 41	2026-02-03
2.8.5	0 / 41	2026-06-17
2.8.3	0 / 41	2026-03-31
2.8.0	0 / 41	2026-01-20
2.7.12	0 / 41	2025-12-19
2.7.11	0 / 41	2025-12-02
2.7.10	0 / 41	2025-11-26
2.7.7	0 / 41	2025-07-30
2.7.6	0 / 41	2025-06-30
2.7.5	0 / 41	2025-06-12
2.7.4	0 / 41	2025-06-11
2.7.3	0 / 41	2025-06-05
2.7.2	0 / 41	2025-05-28
2.7.1	0 / 41	2025-04-24
2.7.0	0 / 41	2025-04-02
2.6.6	0 / 41	2025-04-01
2.6.5	0 / 41	2025-03-28
2.6.4	0 / 41	2025-03-18
2.6.3	0 / 41	2025-03-05
2.6.2	0 / 41	2025-02-28
2.6.1	0 / 41	2025-02-26
2.6.0	0 / 41	2025-02-19
2.5.3	0 / 41	2025-01-31
2.5.2	0 / 41	2024-11-22
2.5.1	0 / 41	2024-11-01
2.5.0	0 / 41	2024-08-02
2.4.0	0 / 41	2024-07-31
2.3.4	0 / 41	2024-07-22
2.3.3	0 / 41	2024-06-24
2.3.2	0 / 41	2024-06-21
2.3.1	0 / 41	2024-06-11
2.3.0	0 / 41	2024-06-10
2.2.3	0 / 41	2024-04-08
2.2.2	0 / 41	2024-03-20
2.2.1	0 / 41	2024-02-08
2.2.0	0 / 41	2023-12-11
2.1.0	0 / 41	2023-11-22
2.0.1	0 / 41	2023-10-19
2.0.0	0 / 41	2023-10-19

v2.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kirill.gatalsky → aleksej-tikhanovich (on 2026-07-03, known maintainer) provenance

This version was published by a different npm account (aleksej-tikhanovich) than the most recent previously approved version (kirill.gatalsky) on 2026-07-03, but aleksej-tikhanovich 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.7.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oat-admin → llecaque (on 2025-04-24, known maintainer) provenance

This version was published by a different npm account (llecaque) than the most recent previously approved version (oat-admin) on 2025-04-24, but llecaque 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.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: marpesia → oat-admin (on 2025-04-02, known maintainer) provenance

This version was published by a different npm account (oat-admin) than the most recent previously approved version (marpesia) on 2025-04-02, but oat-admin 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.6.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: marpesia → oat-admin (on 2025-04-01, known maintainer) provenance

This version was published by a different npm account (oat-admin) than the most recent previously approved version (marpesia) on 2025-04-01, but oat-admin 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.6.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oat-admin → marpesia (on 2025-03-28, known maintainer) provenance

This version was published by a different npm account (marpesia) than the most recent previously approved version (oat-admin) on 2025-03-28, but marpesia 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.6.4

1 finding

LOW No provenance attestation provenance

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

v2.6.3

1 finding

LOW No provenance attestation provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.3

1 finding

LOW No provenance attestation provenance

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

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.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.

v2.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.

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: shaveko → oat-admin (on 2023-10-19, known maintainer) provenance

This version was published by a different npm account (oat-admin) than the most recent previously approved version (shaveko) on 2023-10-19, but oat-admin 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.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.