← Home

@ajna-inc/npmvc

npm Repository Homepage

Verifiable-credential supply chain compliance for npm. Sign attestations, verify dependencies, revoke compromised packages.

13
Versions
Apache-2.0
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

vinaysingh8866

Keywords

supply-chainsecuritynpmverifiable-credentialsdidattestationsbomprovenancesigningverification

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tar AI (phantom-deps): tar is a declared runtime dep used indirectly in this CLI tool; phantom-dep heuristic fires due to no direct import. ai
phantom-deps phantom-dep:jose AI (phantom-deps): jose is a declared runtime dep for JWT/JWS operations; indirect usage pattern expected in this attestation tool. ai
phantom-deps phantom-dep:@cyclonedx/cyclonedx-npm AI (phantom-deps): cyclonedx-npm is invoked as a CLI subprocess for SBOM generation, not imported directly. ai

Versions (showing 13 of 13)

Version Deps Published
0.4.1 11 / 4
0.4.0 11 / 4
0.3.3 11 / 4
0.3.2 11 / 4
0.3.1 11 / 4
0.3.0 11 / 4
0.2.2 11 / 4
0.2.1 11 / 4
0.2.0 11 / 4
0.1.3 11 / 4
0.1.2 11 / 4
0.1.1 11 / 4
0.1.0 11 / 4

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.3

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

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

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

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

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

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