@peerbit/identity-access-controller
Access controller that operates on a DB
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 6.0.61 | 7 / 3 | |
| 6.0.60 | 7 / 3 | |
| 6.0.59 | 7 / 3 | |
| 6.0.58 | 7 / 3 | |
| 6.0.57 | 7 / 3 | |
| 6.0.56 | 7 / 3 | |
| 6.0.55 | 7 / 3 | |
| 6.0.54 | 7 / 3 | |
| 6.0.53 | 7 / 3 | |
| 6.0.52 | 7 / 3 | |
| 6.0.51 | 7 / 3 | |
| 6.0.50 | 7 / 3 | |
| 6.0.49 | 7 / 3 | |
| 6.0.48 | 7 / 3 | |
| 6.0.47 | 7 / 3 | |
| 6.0.46 | 7 / 3 | |
| 6.0.45 | 7 / 3 | |
| 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.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.