@peculiar/asn1-x509-logotype
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): PeculiarVentures org migrated to GitHub Actions CI publishing; SLSA attestation confirms integrity. | ai | |
| provenance | missing-githead | AI (provenance): CI/CD publishing via GitHub Actions commonly omits gitHead; SLSA provenance attestation compensates. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI migration is consistent with legitimate maintenance resumption for this org. | ai | |
| phantom-deps | phantom-dep:asn1js | AI (phantom-deps): asn1js is a transitive peer dep used via @peculiar/asn1-schema; phantom-dep false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 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.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.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.