← Home

@developer-overheid-nl/don-register-layouts

npm Repository Homepage

The layouts for the API- and OSS registers

3
Versions
EUPL-1.2
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

joostfarlapasibunsetonix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:i18next AI (phantom-deps): i18next is a runtime dep used via config/framework integration, not direct import. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): TypeScript listed as dep for raw .ts exports; not directly imported. ai
phantom-deps phantom-dep:@utrecht/component-library-css AI (phantom-deps): CSS package referenced in config/stylesheets, not JS imports. ai
phantom-deps phantom-dep:@rijkshuisstijl-community/design-tokens AI (phantom-deps): Design tokens referenced via CSS/config, not direct JS import. ai
phantom-deps phantom-dep:@rijkshuisstijl-community/components-css AI (phantom-deps): CSS package referenced in config/stylesheets, not JS imports. ai
phantom-deps phantom-dep:@rijkshuisstijl-community/components-react AI (phantom-deps): React components likely re-exported; phantom-dep heuristic mismatch. ai
phantom-deps phantom-dep:@developer-overheid-nl/don-register-locales AI (phantom-deps): Same-org locale package; likely config-level reference. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.0 9 / 0
1.0.2 9 / 0
1.0.1 9 / 0

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

v1.0.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.

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