← Home

@flusys/nestjs-iam

Identity and Access Management (IAM) module for NestJS applications

29
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sfd.mhrana

Keywords

nestjsiamrbacpermissionsrolesaccess-control@flusys

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all @flusys packages; not a security risk for this ecosystem. ai

Versions (showing 29 of 29)

Version Deps Published
6.1.1 2 / 0
6.1.0 2 / 0
6.0.2 2 / 0
6.0.1 2 / 0
6.0.0 2 / 0
5.5.0 2 / 0
5.4.1 2 / 0
5.4.0 2 / 0
5.3.1 2 / 0
5.3.0 2 / 0
5.2.0 2 / 0
5.1.3 2 / 0
5.1.2 2 / 0
5.1.1 2 / 0
5.1.0 2 / 0
5.0.4 2 / 0
5.0.3 2 / 0
5.0.1 2 / 0
5.0.0 2 / 0
4.1.1 2 / 0
4.1.0 2 / 0
4.0.2 2 / 0
4.0.1 2 / 0
3.0.1 2 / 0
3.0.0 2 / 0
2.0.0 2 / 0
1.1.0 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0

v6.1.1

1 finding
INFO No provenance attestation provenance

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

v6.1.0

1 finding
INFO No provenance attestation provenance

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

v6.0.2

1 finding
INFO No provenance attestation provenance

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

v6.0.1

1 finding
INFO No provenance attestation provenance

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

v6.0.0

1 finding
INFO No provenance attestation provenance

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

v5.5.0

1 finding
INFO No provenance attestation provenance

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