← Home

@peculiar/asn1-ntqwac

npm Repository Homepage

ASN.1 schema for ntQWAC profile extensions, including domain-name roles, activity descriptions, GDPR attestations, insurance values, and valuation rankings.

6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

rmhriskmicroshineyury.strozhevskypeculiarventuresapilgukdonskovworldthirteen

Keywords

asnasn1ntqwacqwacx509gdprcertificate-profile

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is cosmetic given Sigstore-signed CI provenance. ai
phantom-deps phantom-dep:asn1js AI (phantom-deps): asn1js is imported transitively via @peculiar/asn1-x509; stable false positive. ai
bogus-package bogus-package AI (bogus-package): Established package with legitimate repo; missing README detail is not indicative of malice. ai

Versions (showing 6 of 6)

Version Deps Published
2.8.0 4 / 0
2.7.0 4 / 0
2.6.1 4 / 0
2.6.0 4 / 0
2.5.0 4 / 0
2.4.0 4 / 0

v2.8.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.7.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.6.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.

v2.6.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.

v2.5.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.

v2.4.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.