← Home

@entur/form

npm Repository Homepage
16
Versions
—
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

oysvalenturaskentandersentestowermagnusrandtysseng-enturfrankwaldalceciliehrrteamplattformkennethngo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org team account takeover on a long-lived @entur scoped package; consistent with internal team restructuring. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with team account addition; no malicious indicators in diff or metadata. ai
dependencies unvetted-dep:@entur/utils AI (dependencies): Sibling package in the same @entur design-system monorepo. ai
dependencies unvetted-dep:@entur/button AI (dependencies): Sibling package in the same @entur design-system monorepo. ai
dependencies unvetted-dep:@entur/typography AI (dependencies): Sibling package in the same @entur design-system monorepo. ai
dependencies unvetted-dep:@entur/tooltip AI (dependencies): Sibling package in the same @entur design-system monorepo. ai
dependencies unvetted-dep:@entur/icons AI (dependencies): Sibling package in the same @entur design-system monorepo. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @entur/form is a scoped design-system package; Levenshtein match to 'cors' is a false positive. ai

Versions (showing 16 of 16)

Version Deps Published
9.3.4 7 / 10
9.3.3 7 / 10
9.3.2 7 / 10
9.3.1 7 / 10
9.3.0 7 / 11
9.2.7 7 / 11
9.2.6 7 / 11
9.2.5 7 / 11
9.2.4 7 / 11
9.2.3 7 / 11
9.2.2 7 / 11
9.2.1 7 / 11
9.2.0 7 / 11
9.1.0 7 / 11
9.0.1 7 / 11
9.0.0 7 / 11

v9.3.4

1 finding
LOW No provenance attestation provenance

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

v9.3.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.

v9.3.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.

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

v9.3.0

1 finding
LOW No provenance attestation provenance

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

v9.2.7

1 finding
LOW No provenance attestation provenance

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

v9.2.6

1 finding
LOW No provenance attestation provenance

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

v9.2.5

1 finding
LOW No provenance attestation provenance

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

v9.2.4

1 finding
LOW No provenance attestation provenance

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

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

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

v9.2.1

1 finding
LOW No provenance attestation provenance

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

v9.2.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.

v9.1.0

1 finding
LOW No provenance attestation provenance

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

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

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