@peculiar/asn1-schema
Decorators for ASN.1 schemas building
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD; SLSA provenance confirms legitimate publish pipeline. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions publish flow omits gitHead; SLSA provenance compensates. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with infrequent releases; 235-day gap is normal for stable libraries. | ai | |
| dependencies | unvetted-dep:pvtsutils | AI (dependencies): pvtsutils is a core PeculiarVentures utility dependency present across all versions of this package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:asn1js | AI (dependencies): asn1js is a core PeculiarVentures dependency that has been present across all versions of this package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@types/asn1js | AI (dependencies): @types/asn1js is a legitimate TypeScript type definitions package for asn1js, appropriate for this TypeScript-based ASN.1 schema library. | ai | |
| phantom-deps | phantom-dep:@types/asn1js | AI (phantom-deps): @types/asn1js is a TypeScript type definition package; it is loaded by convention via TypeScript's type resolution, not direct imports. This is expected and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): PeculiarVentures packages consistently lack Sigstore provenance; this is a known gap for this publisher, not a risk indicator. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.0 | 3 / 0 | |
| 2.3.15 | 3 / 0 | |
| 2.3.13 | 3 / 0 | |
| 2.3.8 | 3 / 0 | |
| 2.3.6 | 3 / 0 | |
| 2.3.3 | 3 / 0 | |
| 2.3.0 | 3 / 0 | |
| 2.2.0 | 3 / 0 | |
| 2.1.9 | 3 / 0 | |
| 2.1.8 | 3 / 0 | |
| 2.1.7 | 3 / 0 | |
| 2.1.6 | 3 / 0 | |
| 2.1.5 | 4 / 0 | |
| 2.1.0 | 4 / 0 | |
| 2.0.44 | 4 / 0 | |
| 2.0.38 | 4 / 0 | |
| 2.0.37 | 4 / 0 | |
| 2.0.36 | 4 / 0 | |
| 2.0.32 | 4 / 0 | |
| 2.0.29 | 4 / 0 | |
| 2.0.27 | 4 / 0 | |
| 2.0.26 | 4 / 0 | |
| 2.0.25 | 4 / 0 | |
| 2.0.23 | 4 / 0 | |
| 2.0.17 | 4 / 0 | |
| 2.0.13 | 4 / 0 | |
| 2.0.12 | 4 / 0 | |
| 2.0.11 | 4 / 0 | |
| 2.0.8 | 4 / 0 | |
| 2.0.7 | 4 / 0 | |
| 2.0.5 | 4 / 0 | |
| 2.0.4 | 4 / 0 | |
| 2.0.3 | 4 / 0 | |
| 2.0.1 | 3 / 0 | |
| 1.1.2 | 2 / 8 | |
| 1.1.1 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.5 | 2 / 8 | |
| 1.0.4 | 2 / 8 | |
| 1.0.3 | 2 / 7 | |
| 1.0.2 | 2 / 9 | |
| 1.0.1 | 2 / 9 |
v2.7.0
3 findingsThis 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.
This version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] 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[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.