← Home

@entur/dropdown

npm Repository Homepage
14
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): Entur org team rotation; publisher has strong track record, no code changes. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with maintainer-added; consistent with org team management, not a takeover. ai
dependencies unvetted-dep:@entur/form AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/icons AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/utils AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/a11y AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/loader AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/tooltip AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/button AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@entur/chip AI (dependencies): Internal @entur monorepo sibling; stable pattern across all versions. ai

Versions (showing 14 of 14)

Version Deps Published
8.1.3 12 / 10
8.1.2 12 / 10
8.1.1 12 / 10
8.1.0 12 / 11
8.0.9 12 / 11
8.0.8 12 / 11
8.0.7 12 / 11
8.0.6 12 / 11
8.0.5 12 / 11
8.0.4 12 / 11
8.0.3 12 / 11
8.0.2 12 / 11
8.0.1 12 / 11
8.0.0 12 / 11

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

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

v8.1.1

1 finding
LOW No provenance attestation provenance

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

v8.1.0

1 finding
LOW No provenance attestation provenance

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

v8.0.9

1 finding
LOW No provenance attestation provenance

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

v8.0.8

1 finding
LOW No provenance attestation provenance

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

v8.0.7

1 finding
LOW No provenance attestation provenance

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

v8.0.6

1 finding
LOW No provenance attestation provenance

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

v8.0.5

1 finding
LOW No provenance attestation provenance

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

v8.0.4

1 finding
LOW No provenance attestation provenance

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

v8.0.3

1 finding
LOW No provenance attestation provenance

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

v8.0.2

1 finding
LOW No provenance attestation provenance

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

v8.0.1

1 finding
LOW No provenance attestation provenance

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

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