← Home

@peerbit/identity-access-controller

npm Repository Homepage

Access controller that operates on a DB

15
Versions
MIT
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

marcus.pousette

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; sparse README and no keywords are consistent across all peerbit packages, not spam. ai
dependencies unvetted-dep:@dao-xyz/borsh AI (dependencies): First-party dependency from same dao-xyz/peerbit monorepo; stable pattern across all versions. ai
dependencies unvetted-dep:@peerbit/crypto AI (dependencies): First-party sibling package from peerbit monorepo. ai
dependencies unvetted-dep:@peerbit/program AI (dependencies): First-party sibling package from peerbit monorepo. ai
dependencies unvetted-dep:@peerbit/document AI (dependencies): First-party sibling package from peerbit monorepo. ai
dependencies unvetted-dep:@peerbit/shared-log AI (dependencies): First-party sibling package from peerbit monorepo. ai

Versions (showing 15 of 15)

Version Deps Published
6.0.42 7 / 3
6.0.39 7 / 3
6.0.30 7 / 3
6.0.29 7 / 3
5.2.14 7 / 3
5.2.13 7 / 3
5.2.4 7 / 3
5.2.3 7 / 3
5.2.2 7 / 3
5.2.1 7 / 3
5.2.0 7 / 3
5.1.3 7 / 3
5.1.2 7 / 3
5.1.1 7 / 3
5.1.0 7 / 3

v6.0.42

1 finding
LOW No provenance attestation provenance

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

v6.0.39

1 finding
LOW No provenance attestation provenance

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

v5.2.14

1 finding
LOW No provenance attestation provenance

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

v5.2.13

1 finding
LOW No provenance attestation provenance

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

v5.2.4

1 finding
LOW No provenance attestation provenance

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

v5.2.3

1 finding
LOW No provenance attestation provenance

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

v5.2.2

1 finding
LOW No provenance attestation provenance

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

v5.2.1

1 finding
LOW No provenance attestation provenance

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

v5.2.0

1 finding
LOW No provenance attestation provenance

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

v5.1.3

1 finding
LOW No provenance attestation provenance

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

v5.1.2

1 finding
LOW No provenance attestation provenance

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

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

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