@enso-ui/tutorials MIT 10 versions

@enso-ui/tutorials

npm Repository Homepage

Tutorial administration pages for Enso UI.

10

Versions

MIT

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

aocneanugandescvlad.chvraftx24manuela.mindroc

Keywords

tutorialsvue

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:vue	AI (phantom-deps): Vue is a peer/config dependency for a Vue component package; not directly imported by design.	ai	2026/04/28
phantom-deps	phantom-dep:pinia	AI (phantom-deps): Pinia is a peer/config dependency for a Vue component package; not directly imported by design.	ai	2026/04/28
phantom-deps	phantom-dep:@enso-ui/forms	AI (phantom-deps): Same-org dependency; phantom-dep heuristic is a stable false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@enso-ui/tables	AI (phantom-deps): Same-org dependency; phantom-dep heuristic is a stable false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:driver.js	AI (phantom-deps): driver.js is a legitimate UI library referenced in config; phantom-dep is a stable false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@fortawesome/vue-fontawesome	AI (phantom-deps): @fortawesome/vue-fontawesome is a well-known icon library; config-only reference is expected for this package.	ai	2026/04/28

Versions (showing 10 of 10)

Version	Deps	Published
5.2.9	4 / 8	2026-04-25
5.2.8	4 / 8	2026-04-17
5.2.7	4 / 8	2026-04-17
5.2.6	4 / 5	2026-04-16
5.2.5	4 / 5	2026-04-13
5.2.3	4 / 5	2026-04-12
5.2.2	7 / 2	2026-04-12
5.2.1	9 / 0	2026-04-10
5.2.0	9 / 0	2026-04-10
5.1.0	9 / 0	2026-04-09

v5.2.9

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. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.7

1 finding

LOW No provenance attestation provenance

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

v5.2.6

1 finding

LOW No provenance attestation provenance

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

v5.2.5

1 finding

LOW No provenance attestation provenance

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

v5.2.3

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

1 finding

LOW No provenance attestation provenance

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

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.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.