@not-govuk/tabs-internal No license 12 versions

@not-govuk/tabs-internal

npm

12

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

daniel-ac-martin

Keywords

react-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New deps are first-party sibling packages, consistent with monorepo versioning.	ai	2026/07/23
dependencies	unvetted-dep:@not-govuk/router	AI (dependencies): First-party sibling package in same monorepo, versioned in lockstep.	ai	2026/07/23
publish-pattern	dormant-publish	AI (publish-pattern): Established monorepo with slow, batch-style release cadence; not account-takeover pattern.	ai	2026/07/23

Versions (showing 12 of 12)

Version	Deps	Published
0.15.3	3 / 7	2025-01-05
0.15.1	3 / 7	2024-11-27
0.15.0	3 / 7	2024-11-10
0.14.0	2 / 7	2024-09-22
0.13.0	2 / 7	2024-09-21
0.12.1	2 / 7	2024-09-10
0.12.0	2 / 7	2024-09-09
0.11.1	2 / 7	2024-09-03
0.11.0	2 / 7	2024-09-01
0.10.0	2 / 7	2024-08-27
0.9.1	2 / 7	2024-08-14
0.9.0	2 / 7	2024-08-01

v0.15.3

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.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.

v0.9.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.