← Home

@stamp-lib/stamp-iam-role-catalog

npm
13
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

yanakayus

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal AWS IAM tooling package; sparse metadata is consistent with monorepo/internal library pattern across all versions. ai
phantom-deps phantom-dep:@aws-sdk/client-sts AI (phantom-deps): AWS SDK packages are often loaded indirectly via credential providers; stable false positive for this package. ai
phantom-deps phantom-dep:@aws-sdk/client-sso-admin AI (phantom-deps): AWS SDK packages may be loaded indirectly; stable false positive for this package. ai
phantom-deps phantom-dep:@aws-sdk/client-identitystore AI (phantom-deps): AWS SDK packages may be loaded indirectly; stable false positive for this package. ai

Versions (showing 13 of 13)

Version Deps Published
0.9.0 12 / 0
0.8.1 12 / 0
0.8.0 12 / 0
0.7.9 12 / 0
0.7.8 12 / 0
0.7.7 12 / 0
0.7.6 12 / 0
0.7.5 12 / 0
0.7.4 12 / 0
0.7.3 12 / 0
0.7.2 12 / 0
0.7.1 12 / 0
0.7.0 12 / 0

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.7.9

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

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

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

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

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

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